Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Appcelerator JIRA by cong ling, 1 year ago
Could not connect to debugger on port 55908
via Appcelerator JIRA by cong ling, 1 year ago
Could not connect to debugger on port 55908
via Appcelerator JIRA by Chris Williams, 1 year ago
Could not connect to debugger on port 53791
via Appcelerator JIRA by Chris Williams, 1 year ago
Could not connect to debugger on port 53791
com.aptana.ruby.internal.debug.core.DebuggerNotFoundException: Could not connect to debugger on port 55908	at com.aptana.ruby.internal.debug.core.commands.AbstractDebuggerConnection.getSocket(AbstractDebuggerConnection.java:93)	at com.aptana.ruby.internal.debug.core.commands.AbstractDebuggerConnection.createCommandConnection(AbstractDebuggerConnection.java:75)	at com.aptana.ruby.internal.debug.core.commands.RubyDebugConnection.connect(RubyDebugConnection.java:22)	at com.aptana.ruby.internal.debug.core.RubyDebuggerProxy.start(RubyDebuggerProxy.java:79)	at com.aptana.ruby.internal.debug.core.launching.RubyDebuggerLaunchDelegate.launch(RubyDebuggerLaunchDelegate.java:139)	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:858)	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:707)	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:700)	at org.radrails.rails.core.RailsServer.start(RailsServer.java:113)	at com.aptana.webserver.ui.internal.actions.StartServerHandler$1.run(StartServerHandler.java:46)	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)