com.aptana.ruby.internal.debug.core.DebuggerNotFoundException: Could not connect to debugger on port 53791

Appcelerator JIRA | Chris Williams | 6 years ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    Now I keep receiving this error whenever I try to debug my ruby application: "C:\Ruby\Ruby192\bin\rubyw.EXE: No such file or directory -- Studio (LoadError)" I checked the error log and it says: {code} !ENTRY org.eclipse.core.jobs 4 2 2011-07-25 09:41:57.161 !MESSAGE An internal error occurred during: "Launching CFE Documentation". !STACK 0 com.aptana.ruby.internal.debug.core.DebuggerNotFoundException: Could not connect to debugger on port 53791 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:113) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:702) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:924) at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1128) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} I've double-checked the windows directory to make sure rubyw.EXE was actually at that location, and it is. The only difference I could find was the capitalization of "exe". It is lowercase in the actual windows directory, but that has no bearing on the error. (I checked.)

    Appcelerator JIRA | 6 years ago | Chris Williams
    com.aptana.ruby.internal.debug.core.DebuggerNotFoundException: Could not connect to debugger on port 53791
  2. 0

    Now I keep receiving this error whenever I try to debug my ruby application: "C:\Ruby\Ruby192\bin\rubyw.EXE: No such file or directory -- Studio (LoadError)" I checked the error log and it says: {code} !ENTRY org.eclipse.core.jobs 4 2 2011-07-25 09:41:57.161 !MESSAGE An internal error occurred during: "Launching CFE Documentation". !STACK 0 com.aptana.ruby.internal.debug.core.DebuggerNotFoundException: Could not connect to debugger on port 53791 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:113) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:702) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:924) at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1128) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} I've double-checked the windows directory to make sure rubyw.EXE was actually at that location, and it is. The only difference I could find was the capitalization of "exe". It is lowercase in the actual windows directory, but that has no bearing on the error. (I checked.)

    Appcelerator JIRA | 6 years ago | Chris Williams
    com.aptana.ruby.internal.debug.core.DebuggerNotFoundException: Could not connect to debugger on port 53791
  3. 0

    The debugger can't access the debug port in some network environment (in my office), but it's success in my home. I'm using wireshark to monitor the traffic, I found that the debugger is trying to connect the dhcp ip address (in my office, it connect to 10.130.xx.xx) , not 127.0.0.1 when it's wrong, it's quite wired. When using Debug Server on a rails project, the debug port is established, but the debugger can't access the debug port. .metadata/.log shows the connection exception. 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)

    Appcelerator JIRA | 3 years ago | cong ling
    com.aptana.ruby.internal.debug.core.DebuggerNotFoundException: Could not connect to debugger on port 55908
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    The debugger can't access the debug port in some network environment (in my office), but it's success in my home. I'm using wireshark to monitor the traffic, I found that the debugger is trying to connect the dhcp ip address (in my office, it connect to 10.130.xx.xx) , not 127.0.0.1 when it's wrong, it's quite wired. When using Debug Server on a rails project, the debug port is established, but the debugger can't access the debug port. .metadata/.log shows the connection exception. 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)

    Appcelerator JIRA | 3 years ago | cong ling
    com.aptana.ruby.internal.debug.core.DebuggerNotFoundException: Could not connect to debugger on port 55908

    Root Cause Analysis

    1. com.aptana.ruby.internal.debug.core.DebuggerNotFoundException

      Could not connect to debugger on port 53791

      at com.aptana.ruby.internal.debug.core.commands.AbstractDebuggerConnection.getSocket()
    2. com.aptana.ruby
      RubyDebuggerLaunchDelegate.launch
      1. com.aptana.ruby.internal.debug.core.commands.AbstractDebuggerConnection.getSocket(AbstractDebuggerConnection.java:93)
      2. com.aptana.ruby.internal.debug.core.commands.AbstractDebuggerConnection.createCommandConnection(AbstractDebuggerConnection.java:75)
      3. com.aptana.ruby.internal.debug.core.commands.RubyDebugConnection.connect(RubyDebugConnection.java:22)
      4. com.aptana.ruby.internal.debug.core.RubyDebuggerProxy.start(RubyDebuggerProxy.java:79)
      5. com.aptana.ruby.internal.debug.core.launching.RubyDebuggerLaunchDelegate.launch(RubyDebuggerLaunchDelegate.java:113)
      5 frames
    3. Debug Core
      LaunchConfiguration.launch
      1. org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
      2. org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:702)
      2 frames
    4. org.eclipse.debug
      DebugUIPlugin$8.run
      1. org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:924)
      2. org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1128)
      2 frames
    5. Eclipse Jobs
      Worker.run
      1. org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
      1 frame