[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-8548) Support auto discovery of remote processes for debugging

[Snjezana Peco (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613117#comment-12613117 ] 

Snjezana Peco commented on JBIDE-8548:
--------------------------------------

I have upgraded this feature. You can install/update it using the mentioned update site.

> The command ("org.jboss.tools.remote.debug.ui5951") is undefined
> The command ("org.jboss.tools.remote.debug.ui.configure") is undefined

I have fixed this. These warnings shouldn't be appearing anymore.

> disconnect debug
> select project 2 - remote debug
> select project 2 - configure

>    "default" remote debug launch is still associated with project 1

Fixed.

> Caused by: sun.jvmstat.monitor.MonitorException: Could not synchronize with target

Fixed. As to the applications started with "suspend=y", I use the following OS commands:
- "netstat -ona -p tcp" on Windows
- "lsof -i -P" on Mac OS X (didn't test it)
- "netstat -nlt -p <PID>" on Linux
However, the main class for those applications can't be shown. The menu option for them looks like: "Unknown, pid=xxxx, port=yyyy".

> Now, right clicking in eclipse will cause a strange lag/hang and all is very sluggish. 

The MonitoredVmUtil.jvmArgs method is slow. You can see that JConsole also opens the "New Connection" dialog very slowly if there are applications started with "suspend=y". I have checked Oracle JDK 1.6 u26, OpenJDK 6 b22 and JDK 1.7 b147.
I am not sure if there is any other way to check if an application has been started in the debug mode. OS commands don't help in this case because the application can be started in the run mode and open a port.
I have improved the speed by removing the property tester that calls this method more times. As a consequence, the "Remote Debug As" menu is always shown. When there are no debuggable applications, the menu contains only the "Configure..." option.

TODO:

- add all the selected projects to the source attachment
- add key bindings

as described in the previous comment.





> 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, lsof.txt, org.jboss.tools.remote.debug.zip, org.jboss.tools.remote.debug1.zip
>
>
> 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