Attempting to connect remote debugging from Eclipse fails with timeout error

Solution Verified - Updated -

Issue

  • When we attempt to remote debug from Eclipse we get "Failed to connect to remote VM. Connection timed out."
  • See error in .log file:
    !MESSAGE Failed to connect to remote VM. Connection timed out.
    !STACK 0
    org.eclipse.jdi.TimeoutException: Timeout occurred while waiting for packet XXXXX.
         at org.eclipse.jdi.internal.connect.PacketReceiveManager.getReply(PacketReceiveManager.java:171)
         at org.eclipse.jdi.internal.connect.PacketReceiveManager.getReply(PacketReceiveManager.java:180)
         at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:174)
         at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:230)
         at org.eclipse.jdi.internal.VirtualMachineImpl.allClasses(VirtualMachineImpl.java:355)
         at org.eclipse.jdi.internal.VirtualMachineImpl.allRefTypes(VirtualMachineImpl.java:382)
         at org.eclipse.jdi.internal.ReferenceTypeImpl.nestedTypes(ReferenceTypeImpl.java:1105)
         at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.addToTargetForLocalType(JavaBreakpoint.java:563)
         at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.createRequests(JavaBreakpoint.java:540)
         at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.addToTarget(JavaBreakpoint.java:498)
         at org.eclipse.jdt.internal.debug.core.breakpoints.JavaLineBreakpoint.addToTarget(JavaLineBreakpoint.java:167)
         at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.breakpointAdded(JDIDebugTarget.java:1190)
         at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.initializeBreakpoints(JDIDebugTarget.java:470)
         at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.initialize(JDIDebugTarget.java:401)
         at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.<init>(JDIDebugTarget.java:275)
         at org.eclipse.jdt.debug.core.JDIDebugModel$1.run(JDIDebugModel.java:160)
         at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
         at org.eclipse.jdt.debug.core.JDIDebugModel.newDebugTarget(JDIDebugModel.java:164)
         at org.eclipse.jdt.debug.core.JDIDebugModel.newDebugTarget(JDIDebugModel.java:124)
         at org.eclipse.jdt.internal.launching.SocketAttachConnector.connect(SocketAttachConnector.java:141)
         at org.eclipse.jdt.internal.launching.JavaRemoteApplicationLaunchConfigurationDelegate.launch(JavaRemoteApplicationLaunchConfigurationDelegate.java:79)
         at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:764)
         at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:614)
         at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:865)
         at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1068)
         at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    

Environment

  • Sun JDK 1.6
  • Connecting to app server running on Windows 2008 Server
  • Connecting from Windows XP
  • Eclipse 3.4.2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content