This content has been marked as final. Show 15 replies
A bit more follow-up...
When I debug the function from 10.1.2 this is the output in the Debugging message window:
Connecting to the database lt10gr2_hr.This output is missing in the debugging message window:
Executing PL/SQL: ALTER SESSION SET PLSQL_DEBUG=TRUE
Executing PL/SQL: CALL DBMS_DEBUG_JDWP.CONNECT_TCP( '169.254.25.129', '1235' )
Debugger accepted connection from database on port 1235.
Debugger disconnected from database.
Disconnecting from the database lt10gr2_hr.
PL/SQL: ALTER SESSION SET PLSQL_COMPILER_FLAGS=INTERPRETED.So, I am wondering if it is really required - it is not there for 10.1.2 and debugging is working fine in that version. Is there some configuration item, etc. that I may have missed?
It's required that PL/SQL code must be compiled in INTERPRETED mode. If your PL/SQL code is stored on the 9i DB, then you will see the PL/SQL: ALTER SESSION SET PLSQL_COMPILER_FLAGS=INTERPRETED is displayed in the message log window. However, since you are running against 10g DB, this message has been deprecated from the JDeveloper. As you said that you could debug just fine using 10.1.2 version, then all I can suggest you to do is the following when you are using 10.1.3 version.
The breakpoint must be set on an executable line of code. If the debugger does not stop, the breakpoint may have not been set on an executable line of code (verify that the breakpoint was verified). Also, verify that the debugging PL/SQL prerequisites were met. In particular, make sure that the PL/SQL program is compiled in INTERPRETED mode. Good luck.
The database is 10g Release 2 (10.2.0.1.0). The package and package body have both been compiled with the compiler flags set to 'interpreted' and 'debug' and, as I say, JDeveloper 10.1.2 and PL/SQL Developer both work with no problems at all. I am thinking there is something that I have not set correctly in JDeveloper 10.1.3 or that something is just plain not working. I have tried from multiple machines and it just blasts right through the function. I turned on database tracing and it actually does call the function, just no breakpoint/step through capabilities...
And just a bit more information...
It seems that the problem only occurs on code that resides in a package body (which all of mine does). Stand-alone procedures and functions appear to be able to be "stepped-through"...
Here's the plsql* settings on the database:
SQL> show parameter plsql- Mark
NAME TYPE VALUE
------------------------------------ ----------- ------------------
plsql_code_type string INTERPRETED
plsql_compiler_flags string INTERPRETED, DEBUG
plsql_debug boolean TRUE
plsql_native_library_subdir_count integer 0
plsql_optimize_level integer 2
plsql_v2_compatibility boolean FALSE
plsql_warnings string DISABLE:ALL
I'm experiencing similar problem: while trying to debug packages (using JPDA listener dbms_debug.connect) i got 'unable to find source file' dialog with missing filename 'PACKAGE_NAME.pls' - choosing any of 4 options does not help..
I tried to create such file and put it on the projects path with no difference.
Packages are interpreted, compiled with debug info and debugger accepts connection obviously.
Same technique worked rather well with previous versions.
Would like to get some sort of feedback as to whetherMark,
this is a known issue etc.
This is now a known issue. It [bug 4630332] will be fixed in the 10.1.3 production release. For now, breakpoints in package bodies don't work.
My understanding is that in order to do debugging you must be able to set at least the initial breakpoint in the procedure you want to debug so that the debugger knows where to start from. So does the fact that you cant set a breakpoint mean that effectively u cannot do any remote debugging on packaged procedures ?
If the answer to this is yes:
1. Is there a workaround ?
2. Is there an older version of JDeveloper is which this problem does not occur ?