Streaming Studio debug launch hangs if breakpoints exist in other modules
Article ID: KB0072235
Updated On:
| Products | Versions |
|---|---|
| TIBCO Streaming | 11.0 |
Description
In StreamBase Studio, when I launch a module for a debug session (using a Debug Run Configuration), if breakpoints are already set anywhere in the project the launch hangs at log message:
(fragment deploy): Listening for transport dt_socket at address: 8000
(fragment deploy): Listening for transport dt_socket at address: 8000
Resolution
This is defect " SB-51953 STUDIO: Debug as EventFlow hangs on launch if any other module has a breakpoint set" which affects version 11.0 and will be fixed in a future version of TIBCO Streaming.
The problem occurs when any module in the fragment project has breakpoints set, apart from the specific module which is being launched. Those modules do not need to be part of the launch.
To work around this issue use the Breakpoints View outside a debug session to delete all breakpoints.
Only add breakpoints in the module to be debugged (the Main EventFlow module pointed to by the Debug Configuration).
After the application is started, additional breakpoints may be added during the session without restriction.
The problem occurs when any module in the fragment project has breakpoints set, apart from the specific module which is being launched. Those modules do not need to be part of the launch.
To work around this issue use the Breakpoints View outside a debug session to delete all breakpoints.
Only add breakpoints in the module to be debugged (the Main EventFlow module pointed to by the Debug Configuration).
After the application is started, additional breakpoints may be added during the session without restriction.
Issue/Introduction
Make sure only the top level module has breakpoints.
Feedback
Yes
No
Powered by
