[JBIDE-22507] Debugging: cannot debug kitchensink, no breakpoint is being hit - Red Hat Issue Tracker

Steps to Reproduce:
Hide

EXEC: create a new application using eap64-basic-s2i and have it imported into a jboss-kitchensink project in your workspace

EXEC: create a server adapter for the new service that was created: eap-app

EXEC: restart the server adapter in debug mode

EXEC: set a brk point in the source of your imported project (ex. MemberResourceRESTService#listAllMembers)

EXEC: open application in your browser so that your break-point is hit

Result:
Breakpoint never gets hit, debugger never shows up
Show
EXEC: create a new application using eap64-basic-s2i and have it imported into a jboss-kitchensink project in your workspace EXEC: create a server adapter for the new service that was created: eap-app EXEC: restart the server adapter in debug mode EXEC: set a brk point in the source of your imported project (ex. MemberResourceRESTService#listAllMembers) EXEC: open application in your browser so that your break-point is hit Result: Breakpoint never gets hit, debugger never shows up

is related to

JBIDE-22513 [launchbar] NPE when null target

relates to

JBIDE-22066 Server adapter: Stopping debugging of OpenShift application should get application back to normal state.