[jbosstools-issues] [JBoss JIRA] (JBIDE-22507) Debugging: cannot debug kitchensink, no breakpoint is being hit

[Andre Dietisheim (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-22507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andre Dietisheim updated JBIDE-22507:
-------------------------------------
    Steps to Reproduce: 
# 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
# ASSERT: notice the following in your Eclipse log:
{code}
java.lang.NullPointerException
	at org.jboss.tools.wtp.server.launchbar.ModuleLaunchConfigurationProvider.getLaunchConfiguration(ModuleLaunchConfigurationProvider.java:76)
	at org.jboss.tools.wtp.server.launchbar.ModuleLaunchConfigurationProvider.launchDescriptorMatches(ModuleLaunchConfigurationProvider.java:128)
	at org.eclipse.launchbar.core.internal.LaunchBarManager.launchDescriptorMatches(LaunchBarManager.java:964)
	at org.eclipse.launchbar.core.internal.LaunchBarManager.getLaunchDescriptor(LaunchBarManager.java:942)
	at org.eclipse.launchbar.core.internal.LaunchBarManager.setActive(LaunchBarManager.java:424)
	at org.eclipse.launchbar.core.internal.LaunchBarManager.access$0(LaunchBarManager.java:423)
	at org.eclipse.launchbar.core.internal.LaunchBarManager$2.launchAdded(LaunchBarManager.java:169)
	at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.run(LaunchManager.java:446)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.notify(LaunchManager.java:433)
	at org.eclipse.debug.internal.core.LaunchManager.fireUpdate(LaunchManager.java:1043)
	at org.eclipse.debug.internal.core.LaunchManager.addLaunch(LaunchManager.java:703)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:834)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
	at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:329)
	at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$4(OpenShiftLaunchController.java:301)
	at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:167)
	at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugUtils.enableDebugMode(OpenShiftDebugUtils.java:88)
	at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.startDebugging(OpenShiftLaunchController.java:181)
	at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.toggleDebugging(OpenShiftLaunchController.java:104)
	at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:91)
	at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
	at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556)
	at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
	at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{code}
# EXEC: set a brk point in the source of your imported project
# EXEC: refresh browser so that your break-point is hit

Result:
Breakpoint never gets hit, debugger never shows up


  was:
# 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
# ASSERT: notice the following in your Eclipse log:
{code}
java.lang.NullPointerException
	at org.jboss.tools.wtp.server.launchbar.ModuleLaunchConfigurationProvider.getLaunchConfiguration(ModuleLaunchConfigurationProvider.java:76)
	at org.jboss.tools.wtp.server.launchbar.ModuleLaunchConfigurationProvider.launchDescriptorMatches(ModuleLaunchConfigurationProvider.java:128)
	at org.eclipse.launchbar.core.internal.LaunchBarManager.launchDescriptorMatches(LaunchBarManager.java:964)
	at org.eclipse.launchbar.core.internal.LaunchBarManager.getLaunchDescriptor(LaunchBarManager.java:942)
	at org.eclipse.launchbar.core.internal.LaunchBarManager.setActive(LaunchBarManager.java:424)
	at org.eclipse.launchbar.core.internal.LaunchBarManager.access$0(LaunchBarManager.java:423)
	at org.eclipse.launchbar.core.internal.LaunchBarManager$2.launchAdded(LaunchBarManager.java:169)
	at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.run(LaunchManager.java:446)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.notify(LaunchManager.java:433)
	at org.eclipse.debug.internal.core.LaunchManager.fireUpdate(LaunchManager.java:1043)
	at org.eclipse.debug.internal.core.LaunchManager.addLaunch(LaunchManager.java:703)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:834)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
	at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:329)
	at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$4(OpenShiftLaunchController.java:301)
	at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:167)
	at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugUtils.enableDebugMode(OpenShiftDebugUtils.java:88)
	at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.startDebugging(OpenShiftLaunchController.java:181)
	at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.toggleDebugging(OpenShiftLaunchController.java:104)
	at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:91)
	at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
	at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556)
	at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
	at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{code}
# EXEC: set a brk point in the source of your imported project
# EXEC: refresh browser so that your break-point is hit

Result:
Breakpoint never gets hit.




> Debugging: cannot debug kitchensink, no breakpoint is being hit
> ---------------------------------------------------------------
>
>                 Key: JBIDE-22507
>                 URL: https://issues.jboss.org/browse/JBIDE-22507
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.4.0.Alpha2
>            Reporter: Andre Dietisheim
>            Assignee: Rob Stryker
>              Labels: debug, openshift_v3
>             Fix For: 4.4.0.Final
>
>




--
This message was sent by Atlassian JIRA
(v6.4.11#64026)