[jbosstools-issues] [JBoss JIRA] Issue Comment Edited: (JBIDE-8548) Support auto discovery of remote processes for debugging
Aslak Knutsen (JIRA)
jira-events at lists.jboss.org
Fri Jul 15 02:19:23 EDT 2011
[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614345#comment-12614345 ]
Aslak Knutsen edited comment on JBIDE-8548 at 7/15/11 2:18 AM:
---------------------------------------------------------------
Seems it has problems auto recreating the launch config?
# select a resource/class, shift + alt + D + D, it connects to your running service
# disconnect from debug mode
# debug as -> debug configuration
# delete all "JBoss Tools Remote Java Application" configurations
# with the same resource/class selected, shift + alt + D + D, nothing happens?
When the configuration is manually deleted, it is not auto recreated. Error log show:
{code:title=Unhandled event loop exception}
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException)
at org.eclipse.swt.SWT.error(SWT.java:4282)
at org.eclipse.swt.SWT.error(SWT.java:4197)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
Caused by: java.lang.NullPointerException
at org.jboss.tools.remote.debug.ui.actions.RemoteLaunchAction.createOrGetDefaultLaunchConfiguration(RemoteLaunchAction.java:148)
at org.jboss.tools.remote.debug.ui.actions.RemoteLaunchAction.launch(RemoteLaunchAction.java:94)
at org.jboss.tools.remote.debug.ui.actions.RemoteLaunchAction.run(RemoteLaunchAction.java:69)
at org.jboss.tools.remote.debug.ui.launching.RemoteJavaApplicationLaunchShortcut.showDialog(RemoteJavaApplicationLaunchShortcut.java:160)
at org.jboss.tools.remote.debug.ui.launching.RemoteJavaApplicationLaunchShortcut.access$0(RemoteJavaApplicationLaunchShortcut.java:148)
at org.jboss.tools.remote.debug.ui.launching.RemoteJavaApplicationLaunchShortcut$1$1.run(RemoteJavaApplicationLaunchShortcut.java:80)
at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:164)
at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:158)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
... 23 more
{code}
Workaround seems to be:
# Debug As -> Configuration
# JBoss Tools Remote Java Application > New
# Close
# Shift + Ctrl + D + D, it now connects again
was (Author: aslak):
Seems it has problems auto recreating the launch config?
# select a resource/class, shift + alt + D + D, it connects to your running service
# disconnect from debug mode
# debug as -> debug configuration
# delete all "JBoss Tools Remote Java Application" configurations
# with the same resource/class selected, shift + alt + D + D, nothing happens?
When the configuration is manually deleted, it is not auto recreated. Error log show:
{code|title=Unhandled event loop exception}
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException)
at org.eclipse.swt.SWT.error(SWT.java:4282)
at org.eclipse.swt.SWT.error(SWT.java:4197)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
Caused by: java.lang.NullPointerException
at org.jboss.tools.remote.debug.ui.actions.RemoteLaunchAction.createOrGetDefaultLaunchConfiguration(RemoteLaunchAction.java:148)
at org.jboss.tools.remote.debug.ui.actions.RemoteLaunchAction.launch(RemoteLaunchAction.java:94)
at org.jboss.tools.remote.debug.ui.actions.RemoteLaunchAction.run(RemoteLaunchAction.java:69)
at org.jboss.tools.remote.debug.ui.launching.RemoteJavaApplicationLaunchShortcut.showDialog(RemoteJavaApplicationLaunchShortcut.java:160)
at org.jboss.tools.remote.debug.ui.launching.RemoteJavaApplicationLaunchShortcut.access$0(RemoteJavaApplicationLaunchShortcut.java:148)
at org.jboss.tools.remote.debug.ui.launching.RemoteJavaApplicationLaunchShortcut$1$1.run(RemoteJavaApplicationLaunchShortcut.java:80)
at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:164)
at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:158)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
... 23 more
{code}
Workaround seems to be:
# Debug As -> Configuration
# JBoss Tools Remote Java Application > New
# Close
# Shift + Ctrl + D + D, it now connects again
> Support auto discovery of remote processes for debugging
> --------------------------------------------------------
>
> Key: JBIDE-8548
> URL: https://issues.jboss.org/browse/JBIDE-8548
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: JBossAS
> Reporter: Aslak Knutsen
> Assignee: Snjezana Peco
> Fix For: 3.3.0.M3, 3.3.x
>
> Attachments: 8548-1.png, 8548-2.png, 8548-3.png, jbide-8548d.png, lsof.txt, org.jboss.tools.remote.debug.zip, org.jboss.tools.remote.debug1.zip, org.jboss.tools.remote.debug2.zip, org.jboss.tools.remote.debug3.zip, remote_java_application.bmml
>
>
> It would be helpful if Eclipse could provide a 'debug as' with auto discover of local java processes, somewhat like jconsole does. Eclipse should also auto associate the debug session with the current project.
> 'debug as' -> 'remote process x'
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list