- This topic has 5 replies, 2 voices, and was last updated 19 years, 2 months ago by
.
-
Posts
-
I use MyEclipseIDE to launch JBoss server. Everything goes fine until I decide to display/inspect some variable/s containing large XML. MyEclipseIDE crashes leaving the JBoss server debug session running.
After restarting MyEclipseIDE how do I make it reattach to the already running JBoss server debug session? I am using the default JBoss debug configuration as provided with MyEclipse IDE. Looking at output of “ps ux” I can see that it has the following line:
…/jboss-4.0.3SP1/bin/run.jar -Xdebug -Xnoagent -Xrunjdwp transport=dt_socket,suspend=y,address=localhost:34332 org.jboss.Main -c default
The localhost:<port> port changes always and when I try to debug attach to that port MyEclipseIDE complains “Failed to connect remote VM. Connection refused.”
For now I stop the server from within MyEclipseIDE and restart it from within again.
Any ideas?
–Sandeep Khanna
Sandeep,
Sorry to hear things are crashing on you. The problem is that JBoss most likely doesn’t know that Eclipse died, so the port isn’t available for connections. I checked with a developer, and assuming the port was being closed properly, you should be able to reconnect. Have you tried waiting a minute or so and seeing if it times out the old broken connection?@support-rkalla wrote:
Sandeep,
Sorry to hear things are crashing on you. The problem is that JBoss most likely doesn’t know that Eclipse died, so the port isn’t available for connections. I checked with a developer, and assuming the port was being closed properly, you should be able to reconnect. Have you tried waiting a minute or so and seeing if it times out the old broken connection?Wait for JBoss or MyEclipse for a minute?
MyEclipse comes up right away with “Unable to connect… connection refused” when I try to debug attach after MyEclipse restart.
Wait for JBoss or MyEclipse for a minute?
JBoss, try and see if it drops the (dead) connection and reopens the port for connections. If not, the only thing I can suggest is launching JBoss externally and use remote deubgging.
I resolved the MyEclipse crash problem by increasing the max heap memory by updating the eclipse.ini file with the following:
-Xmx1024m instead of the previous -Xmx640m
Now, MyEclipseIDE does not crash so there is no issue of trying to reattach the orphaned JBoss debug server session. Altough it would have been very nice to be able to reattach MyEclipseIDE to a running JBoss debug server session.
–Sandeep Khanna
