Editing Several Package Body Makes SQL Developer to Hang Against Database 12.2.0.1

(Doc ID 2337119.1)

Last updated on DECEMBER 08, 2017

Applies to:

Oracle SQL Developer - Version 1.5.0.52 to 17.3.1
Information in this document applies to any platform.

Symptoms

Editing several package body objects at the same time, makes SQL Developer to hang.

Issue reproduced in 17.3.1 and other old versions against 12.2.0.1 database.

If connected to a 11.2.0.4 database, this behavior is not shown.

 

Thread dump shows when SQL Developer is hanging show no potential Deadlock situation, however many threads similar to as below are in Blocked state.

Thread 72: (state = BLOCKED)

- java.lang.Thread.sleep(long) @bci=0 (Compiled frame; information may be imprecise)

- oracle.dbtools.raptor.plsql.BackgroundParser$1.construct() @bci=21, line=158 (Interpreted frame)

- oracle.dbtools.raptor.utils.NamedSwingWorker$2.run() @bci=8, line=115 (Interpreted frame)

- java.lang.Thread.run() @bci=11, line=748 (Interpreted frame)

Thread 71: (state = BLOCKED)

- java.lang.Thread.sleep(long) @bci=0 (Compiled frame; information may be imprecise)

- oracle.dbtools.raptor.plsql.BackgroundParser$1.construct() @bci=21, line=158 (Interpreted frame)

- oracle.dbtools.raptor.utils.NamedSwingWorker$2.run() @bci=8, line=115 (Interpreted frame)

- java.lang.Thread.run() @bci=11, line=748 (Interpreted frame)

Thread 70: (state = BLOCKED)

- java.lang.Thread.sleep(long) @bci=0 (Compiled frame; information may be imprecise)

- oracle.dbtools.raptor.plsql.BackgroundParser$1.construct() @bci=21, line=158 (Interpreted frame)

- oracle.dbtools.raptor.utils.NamedSwingWorker$2.run() @bci=8, line=115 (Interpreted frame)

- java.lang.Thread.run() @bci=11, line=748 (Interpreted frame)

 

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms