[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Aslak Knutsen commented on JBIDE-8548: -------------------------------------- JConsole seems to use the sun.jvmstat API to discover the processes: {code} import java.util.HashMap; import java.util.Map; import java.util.Set; import org.junit.Test; import sun.jvmstat.monitor.HostIdentifier; import sun.jvmstat.monitor.MonitoredHost; import sun.jvmstat.monitor.MonitoredVm; import sun.jvmstat.monitor.MonitoredVmUtil; import sun.jvmstat.monitor.VmIdentifier; /** * LocalJVMTestCase * * @author <a href="mailto:aslak@redhat.com">Aslak Knutsen</a> * @version $Revision: $ */ public class LocalJVMTestCase { @Test public void shouldBeAbleToFindAllLocalVMs() throws Exception { MonitoredHost host = MonitoredHost.getMonitoredHost(new HostIdentifier((String)null)); Set<Integer> vmPids = host.activeVms(); for(Integer vmPid : vmPids) { System.out.println("PID: " + vmPid); MonitoredVm vm = host.getMonitoredVm(new VmIdentifier(String.valueOf(vmPid))); System.out.println("version: " + MonitoredVmUtil.vmVersion(vm)); System.out.println("jvmArgs: " + MonitoredVmUtil.jvmArgs(vm)); System.out.println("jvmFlags: " + MonitoredVmUtil.jvmFlags(vm)); System.out.println("attachable: " + MonitoredVmUtil.isAttachable(vm)); Map<String, String> arguments = getArguments(MonitoredVmUtil.jvmArgs(vm)); System.out.println("jdwp: " + arguments.get("-Xrunjdwp:transport")); System.out.println(); } } private Map<String, String> getArguments(String args) { Map<String, String> arguments = new HashMap<String, String>(); for(String argument : args.split(" ")) { if(argument.length() == 0) { continue; } String[] nameValue = argument.split("=", 2); if(nameValue.length == 1) { arguments.put(nameValue[0], nameValue[0]); } else { arguments.put(nameValue[0], nameValue[1]); } } return arguments; } } {code} Possible output (JBoss AS 6.0.0.Final VM on Linux): *PID*: 4589 *version*: 19.0-b09 *jvmArgs*: -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n -Djava.net.preferIPv4Stack=true -Dprogram.name=run.sh -Djava.library.path=/home/aslak/dev/servers/jboss-6.0.0.Final/bin/native/lib64 -Djava.endorsed.dirs=/home/aslak/dev/servers/jboss-6.0.0.Final/lib/endorsed *jvmFlags*: *attachable*: true *jdwp: dt_socket,address=8787,server=y,suspend=n* -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-8548: --------------------------------------- Assignee: Snjezana Peco (was: Rob Stryker) Fix Version/s: 3.3.x 3.3.0.M2 3.3.0.M3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-8548: -------------------------------------- Aslak, Max, The action you described would open a dialog similar to the Remote Java Application launch configuration dialog? The user would get ports for all the application started in the debug mode and would be able to select some of them. The action would be active only when starting Eclipse using Oracle or Open JDK >= 1.6. Do you agree? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-8548: -------------------------------------------- Yes and Yes to both Aslak and Snejzana ;) The flow would be to have Debug As -> Remote application... (try to only enable it when relevant to avoid cluttering the menu always, maybe only enable it on project root nodes ?) Then show the list of running applications with all the information that the API can/will provide (ports, vmargs etc.) so its easier to find the possible app and then simply setup that remote process via the standard JDT/Debug Attach to remote java app launch configs. It should also be possible to run it explicitly without the "Debug As..." so providing a Command that users can invoke via Ctrl+3 or via the Debug menu would be perfect too. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-8548: -------------------------------------- I have created this feature. It can be tested using the http://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/org.jboss.tool... update site. The source code is attached. Neither it is possible to contribute a menu to the "Debug As" menu nor to change a label in the launchShortcuts extension point. I have had to add a new menu - "Remote Debug As" to the main context menu. It is visible when some Java project is selected and when there is an application on a local machine that is ready to debug. The menu contains all debuggable applications and the additional item "Configure..." that serves to open the Debug Configurations dialog. The user can configure source attachments using that dialog. The attached screenshots show the Launch Configuration dialog and the "Remote Debug As" action when starting Eclipse on a local machine and JBoss AS 7 in the debug mode. The feature requires Eclipse to be started using a JDK or some JDK runtime to be added to the Installed JREs preference page. tools.jar is being added dynamically from some of those JDK and isn't included in any plugin. I have tested this feature on Windows and Linux. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Aslak Knutsen commented on JBIDE-8548: -------------------------------------- I'm seeing these, but they might be expected? {code} The command ("org.jboss.tools.remote.debug.ui5951") is undefined The command ("org.jboss.tools.remote.debug.ui.configure") is undefined {code} The launch configuration does not change "Project" after first creation. # select project 1 - remote debug # select project 1 - configure ** "default" remote debug launch will be associated with project 1 # disconnect debug # select project 2 - remote debug # select project 2 - configure ** "default" remote debug launch is still associated with project 1 Just tested it for 5 min, but really nice! :) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-8548: -------------------------------------- Will fix it. Commands have to be defined if we want to add key bindings (CTRL-1 ..., for instance). I think key bindings don't mean to much in this case because they have to be defined dynamically and the user can't know what key binding is associated with some application. However if you think key bindings would be usable here, I will add them. This is a bug. Will fix it ASAP. I will also add the following functionality: - when the user selects both of the projects (or more than two projects), all the selected projects will be included in the source attachment. I have noticed that problem. It happens when the application is started with the "suspend=y" option and no debug session is attached. The MonitoredVmUtil.jvmArgs and MonitoredVmUtil.isAttachable methods throw this exception (you can also check this using your snippet). JConsole shows only PID for such applications and it isn't possible to connect to them. We can skip the isAttachable method, but we can't find any port without the jvmArgs method. It seems we can't discover a suspended application this way. I will try to find a solution for this issue. Since we can find PID of an application, I will try to find a port that is opened by the application. I think this can be performed using netstat on Linux and Windows and lsof on Mac OS X. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-8548: -------------------------------------- It is possible to perform that. I will add a preference page that will contain the following: - description (JBoss AS, Maven, Eclipse...) - port - key binding - show the description (y/n) If you define "JBoss AS", 8787,ctrl+d+1,y when the plugin finds the application on the 8787 port, the command will be shown as follows: "JBoss AS E:\jboss-modules.jar, port=8787, pid=xxxx". The action will be associated with the ctrl+d+1 key binding. If you have Mac, could you please send me the output of the "lsof -i -P" command? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Snjezana Peco updated JBIDE-8548: --------------------------------- Attachment: org.jboss.tools.remote.debug1.zip -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-8548: -------------------------------------- I have added the following features: - when the user selects more projects and calls a debug session or the "Configure..." action, all the selected projects will be added to the source attachment - the preference page shown in the jbide-8548d.png. The user can define 10 key bindings for 10 debug sessions. The key bindings are Ctrl+d+0 - Ctrl+d+9. The user can define a port, description and decide whether the description to show in the menu. The key bindings are defined only in the default scope. The user can't change or add a key sequence - Eclipse doesn't allow updating key bindings. The "Discover Remote Applications" checkbox has been introduced for the performance reason. It is set to true by default. The plugin will discover remote processes for debugging when the user opens the "Remote Debug As" menu. If the user has a lot of debug sessions started with the "suspend=y" option, showing the "Remote Debug As" menu could take some time. The user can uncheck the "Discover Remote Applications" checkbox in that case. The plugin won't auto discover remote processes for debugging, but will add the "Discover Remote Applications Ctrl+d+d" action to the "Remote Debug AS" menu. The user can call this action whenever he wants (when starting or stopping some remote application,for instance). The new plugin has been added to the above mentioned update site. Attached is the new source code. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-8548: -------------------------------------------- Snjezana, why wouldn't this be better done via launch shortcuts ? http://help.eclipse.org/indigo/nftopic/org.eclipse.platform.doc.isv/refer... Introducing a new different launch type I don't see the value of since it prevents using it together with the "normal" launches? I'm not fully following what the keyboard shortcuts are good for ? These could be automatically found by just looking at existing launches to find a match would it not ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-8548: --------------------------------------- Attachment: remote_java_application.bmml here is my suggestion expressed as a mockup. Hope it makes it more clear. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-8548: -------------------------------------- Aslak, I can reproduce your issue related to the source lookup. It happens because the Maven classpath container adds only the output directory (target/classes) to the classpath. Eclipse can't find source on the basis of the output directory. The same issue happens when creating a debug session using the Eclipse's Remote Java Application configuration. It can be solved. I will check if it is possible to use MavenRuntimeClasspathProvider without adding m2e dependencies to the remote.debug plugin. M2eclipse uses MavenRuntimeClasspathProvider to solve classpath dependencies. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-8548: -------------------------------------- OK The user starts and stops remote configurations dynamically. He can never be sure that the "last launched" configuration is the one he wants to start. This shortcut won't help so much if the user has more remote applications. The plugin has been created for those users that start/stop a lot of remote applications. That's why "Always select the first one so you can always just press finish and not have to click in the table" from your mockup won't be helpful. Every time when calling the "Remote Java Application" action, the user will likely get different remote applications and will have to review them in order to decide what of them to start. Would the "Remote Java Application..." dialog be started always when calling the "Remote Java Application" action? If so, the user will have to click the "Cancel" button every time when calling this action and when he doesn't want the plugin to discover remote applications. If not, we will have to add the "Discover Remote Application" action somewhere. The plugin creates a configuration (the default) the first time when calling an action and doesn't create it again. However, the plugin has to change some configuration attributes: the selected projects, port ... If those attributes are the same as the attributes of the previous launch configuration, nothing will be changed. The user can configure some additional configurations with different source attachments, the plugin will use the one that the user marked as the default (see the 8548-1.png screenshot). I understand why you want we to remove the "Remote Debug As" menu. However, now the user has to click many times to start a launch configuration: start the action, potentially cancel the "Remote Java Application..." progress dialog, select the configuration in the "Remote Java Application..." dialog, click Finish. The "Automatically connect if only one application found" checkbox won't help. Users that debug only one application doesn't need this plugin at all. They can create the standard Eclipse Remote Java Application configuration for that application. The remote debug plugin is intended for those users that use a lot of launch configurations. Aslak says, he uses two app servers, 2 eclipse, a few servlet containers and some maven builts... What is your opinion about adding the "Disable Remote Debug As menu" preference (true by default)? The "Remote Debug As" menu wouldn't be shown by default and the remote debug plugin wouldn't be started. Those users that want to use this plugin, would have to enable this property, and only in that case this menu would be shown. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-8548: -------------------------------------- I will create the UI as you required. I wanted to enable the user to select more projects that would be added as the default attachment. The Eclipse's Remote Java Application configuration adds only the first selected project. This can also be performed by changing a source path computer of the Eclipse's Remote Java Application configuration, but that would be changing the standard Eclipse Remote Configuration. "project selection, port" aren't the only criterias when selecting some configuration. The user can also use some additional source attachments that there aren't in his workspace. For example, when the user tests Arquillian on JBoss AS, he will want to add some libraries from JBoss AS, when testing it on Glassfish, he will want to add Glassfish libraries ... The user will create separate configurations on JBoss AS and Glassfish, but how to choose what configuration to launch? What will the plugin do if it can't find a corresponding "project selection, port"? Would we create a different configuration for every "project selection, port" combination? That would mean creating a lot of launch configurations. Would we change an existing remote configuration? When using the standard Eclipse Remote Java Application configuration, we mustn't change it because we can't know if the user has created it for other purpose. It is likely that adding some new potential feature to this plugin won't be possible to do using the standard Eclipse remote configuration. That's why I have created a separate type of a launch configuration. It is similar to the standard Eclipse remote configuration, but has a separate source path computer. This way, we can add all selected projects to the default attachment and create a separate Launch Configuration dialog. The "default" launch configuration is created if there isn't any JBoss remote launch configuration. The user can create more different configurations in order to be able to add different source attachments for different applications. When starting debugging automatically (using a menu or shortcut), the plugin uses a configuration that he marks as the default. The plugin checks and, if necessary, changes the selected projects and the port of that configuration and launches the configuration. The user's additional source attachments won't be changed. If the user wants to start a non-default configuration with different attachments, he can call the "Configure..." action or change the default configuration. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-8548: -------------------------------------- I have created the UI as described in the mockup. The Alt+Shift+D, D key binding is associated with the Remote Java Application..." action. The Remote Java Application... dialog has the Configure..., Finish and Cancel button. The "Name" field contains the pid of VM. The Ctrl+d+[0-9] key binding, the Remote Debug As menu and the Remote Debug preferences page have been removed. Do you want me to add the "Automatically connect if only one application found" button to the preference page? Aslak, I think I have solved the issue related to the source lookup. Namely, m2eclipse configures a source path provider and class path provider for the following launch configurations: - Java Application - JUnit test - TestNG test but doesn't configure it for a Remote Java Application I have added a source path computer to our configuration that creates a source attachment the same way in which m2eclipse configures a Java Application configuration. I haven't added any m2e dependency. Max, I am still using a separate configuration type. If that isn't a good solution for you, I will try to use the Eclipse's Remote Java Application and add an attribute to the launch config as you suggested. There is a possibility for a conflict if some other plugin would change source path computer of the Eclipse's Remote Java Application. M2eclipse could add such a source path computer. You can add other projects manually, but our Remote Java Application adds automatically all selected projects as well as maven dependencies from the workspace. adds automatically all selected projects and maven dependencies from the workspace to the default source attachment. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-8548: -------------------------------------------- Snjezana, sounds great with the ui stuff i'll take a look tomorrow if I got any additional comments. Where is the source for this ? Can only see binary commits to your workspace ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Aslak Knutsen commented on JBIDE-8548: -------------------------------------- It seems it doesn't work to Delete a "JBoss Tools Remote Java Application" configuration. I try to delete one that was auto generated, it is removed from the menu and all seems ok. But if I create a new one, the one i deleted pops back up? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-8548: -------------------------------------- If you call our remote debug session, the plugin creates the default launch configuration automatically if there isn't any. To remove all configurations, call Debug As>Run Configurations... and remove them. If you call Debug As>Run Configurations... again, you will see that there isn't any configuration. A configuration won't created until you call some remote debug session. Yes, it has been removed. The new UI doesn't require preferences. We could add that preference. For now, start two or more remote processes and call Debug As>Remote Java Application and you will get the Remote Java Application dialog. Have maven dependencies now been added correctly to the source attachment ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Aslak Knutsen commented on JBIDE-8548: -------------------------------------- Yes, the Maven deps seems to be working quite nicely! :) Is this something we push/report upstream to m2e as well? Since it seems they have the same issue with the 'normal' remote configurations. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] 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 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Snjezana Peco updated JBIDE-8548: --------------------------------- Attachment: org.jboss.tools.remote.debug4.zip -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-8548: -------------------------------------- Fixed -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-8548: -------------------------------------------- Just updated - this UI is *much* better IMO - no blockage and its informative ;) I found a few "gotchas": * The progress bar shows "Discover VM PID=489" when waiting for a java that is waiting for connection. That's not very clear to the user what that means and how many processes does it need to wait for ;) I suggest something like "1 out of 3: Discovering port, main class and arguments for process id 489" * Putting in background and starting a second "Remote Java Application" causes two scans to occur and wait for each other and eventually show the main dialog twice. I suggest showing a dialog saying "Remote Java Application scan already in progress. Please wait for it to be complete." and then if doable have a "Bring scan to foreground" button next to a "Ok" and "Try again" button. * When Class is Unknown it just says Unknown in the class column - I would leave it blank or put "<Unknown>" to signify the class is actually not named Unknown. * Name column I assume should actually be PID or Process ID ? * Finish is probably better named as "Connect" or "Launch" ? * Using the name "Default" is not really good for default configuration - I suggest using the same name Run As/Debug As would give to a launch (i.e. the project name). In case of multiple projects selected then I would use "myapp + N more" where myapp is the project for the first element and N is the number of projects. Or if just to be simple just "myapp" Maybe add "Remote " as prefix ?, so it becomes "Remote myapp" ? * It seems I can't do Remote Debug on other selections than a Project resource ? Couldn't it just take the project of the current selected resource ? * ...and I still think using normal Remote Java Applications config would be the best approach for this functionality; and allow user to choose if there are any ambiguity. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Snjezana Peco updated JBIDE-8548: --------------------------------- Attachment: JBossRemoteConfiguration.png RemoteJavaApplication1.png -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Libor Zoubek commented on JBIDE-8548: ------------------------------------- Snjeza, do I need to do something special when running apps to show up among remote applications? My jps says: {noformat} 4422 org.eclipse.equinox.launcher_1.2.0.v20110502.jar 5098 Jps 3425 jiraclient.jar 5008 Main {noformat} Remote debugger in JBossTools is not able to find anything. (It's asking to repeat searching) I'm on oracle jdk 1.6.027 linux x86, JBT 3.3.0.M3-H18 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-8548: -------------------------------------- When you start AS 7 in the debug mode using JBoss Tools, you are already connected to the remote application and can't be connected again. To start AS 7 from the command line, use: Linux: export JAVA_OPTS="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=1044" standalone.sh Windows: set JAVA_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=1044 standalone.bat -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Libor Zoubek commented on JBIDE-8548: ------------------------------------- verified on JBT 3.3.0.M3-H18 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin... ] Isaac Rooskov closed JBIDE-8548. -------------------------------- Resolution: Done Re-closing now that release note text has been written -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira