APAR status
Closed as program error.
Error description
Error Message: JDI stepping out does not work as expected. In the JDI test, the debuggee has methods1-5, method1 calls method2, method2 calls method3 etc. The main method just calls method1. When the breakpoint set at method5 hits, the debugger request step out 5 times in a loop without disabling stepRequest. As a result, the execution point cannot be moved to each method sequentially(method4, method3, etc.) But with the Oracle SDK, it works fine. So the problem might be in our JDWP module. . Stack Trace: N/A . N/A
Local fix
Call StepRequest.disable() in the loop after step out event being triggered, then enable it again in the next loop.
Problem summary
The problem is caused when step out request being used multiple times. JDWP module doesn't handle this scenario well.
Problem conclusion
This defect will be fixed in: 6.0.0 SR15 7.0.0 SR6 7.1.0 . JDWP module has be enhanced to support this scenario mentioned above.
Temporary fix
N/A
Comments
APAR Information
APAR number
IV46136
Reported component name
JAVA CLASS LIBS
Reported component ID
620700130
Reported release
600
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-07-25
Closed date
2013-08-06
Last modified date
2014-01-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
JAVA CLASS LIBS
Fixed component ID
620700130
Applicable component levels
R600 PSY
UP
R700 PSY
UP
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCVQ3Y","label":"Java Class Libraries"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
01 January 2014