Community
Participate
Working Groups
I had set to show monitor information in the debug view and was debugging Eclipse. I receive an error dialog and the following is in the log: !MESSAGE Exception processing debug async queue !STACK 0 org.eclipse.jdi.TimeoutException: Timeout occurred while waiting for packet 18930 at org.eclipse.jdi.internal.connect.PacketReceiveManager.getReply (PacketReceiveManager.java:163) at org.eclipse.jdi.internal.connect.PacketReceiveManager.getReply (PacketReceiveManager.java:172) at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:174) at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:192) at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:207) at org.eclipse.jdi.internal.ObjectReferenceImpl.monitorInfo (ObjectReferenceImpl.java:136) at org.eclipse.jdi.internal.ObjectReferenceImpl.waitingThreads (ObjectReferenceImpl.java:181) at org.eclipse.jdt.internal.debug.core.model.JDIObjectValue.getWaitingThreads (JDIObjectValue.java:289) at org.eclipse.jdt.internal.debug.ui.monitors.JavaMonitor.update (JavaMonitor.java:132) at org.eclipse.jdt.internal.debug.ui.monitors.JavaMonitor.refresh (JavaMonitor.java:218) at org.eclipse.jdt.internal.debug.ui.monitors.JavaMonitorThread.refresh (JavaMonitorThread.java:272) at org.eclipse.jdt.internal.debug.ui.monitors.JavaMonitor.refresh (JavaMonitor.java:223) at org.eclipse.jdt.internal.debug.ui.monitors.JavaMonitorThread.refresh (JavaMonitorThread.java:272) at org.eclipse.jdt.internal.debug.ui.monitors.ThreadMonitorManager$RefreshAndDetec tDeadlock.run(ThreadMonitorManager.java:216) at org.eclipse.debug.core.DebugPlugin$AsynchJob.run(DebugPlugin.java:983) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
Darins, are you still seeing these Timeout exceptions on this weeks I-builds? I suspect these may have been fixed by bug 83962.
These are what are filling my log today ( I have the monitor stuff turned on): org.eclipse.jdi.TimeoutException: Timeout occurred while waiting for packet 1413 at org.eclipse.jdi.internal.connect.PacketReceiveManager.getReply (PacketReceiveManager.java:163) at org.eclipse.jdi.internal.connect.PacketReceiveManager.getReply (PacketReceiveManager.java:172) at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:174) at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:192) at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:207) at org.eclipse.jdi.internal.ThreadReferenceImpl.threadGroup (ThreadReferenceImpl.java:454) at org.eclipse.jdt.internal.debug.core.model.JDIThread.getUnderlyingThreadGroup (JDIThread.java:1669) at org.eclipse.jdt.internal.debug.core.model.JDIThread.determineIfSystemThread (JDIThread.java:365) at org.eclipse.jdt.internal.debug.core.model.JDIThread.initialize (JDIThread.java:221) at org.eclipse.jdt.internal.debug.core.model.JDIThread.<init> (JDIThread.java:204) at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.createThread (JDIDebugTarget.java:443) at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget$ThreadStartHandler.han dleEvent(JDIDebugTarget.java:1750) at org.eclipse.jdt.internal.debug.core.EventDispatcher.dispatch (EventDispatcher.java:137) at org.eclipse.jdt.internal.debug.core.EventDispatcher.run (EventDispatcher.java:221) at java.lang.Thread.run(Thread.java:534)
any idea how to reproduce them? I'm not having any luck.
I turn on show monitor information and just start self hosting / working as usual. The problems go from there. Have you tried 3 level deep debugging Host-->Target-->Target?
What VM are you using?
1.4.2_03-b02..I guess that is getting old...
I am downloading a newer VM and see if that cleans things up
I tested on IBM 1.4.2 (J9VM - 20040916_0908_lHdSMR) and Sun 1.4.2_07-b05 (and apple 1.4.2_05-141.3, but it doesn't give out monitor information) I did see some strange VM disconnected exceptions with the IBM VM, but nothing reproducible. Haven't seen any timeout exceptions.
I am still able to reproduce (inconsistently) on 1.4.2_07
The line numbers in comment #2 don't match our current code. Line 163 should be throwing a VMDisconnectedException.
Darins, could you update/export your jdt.debug plugin and run on it? I've made a couple small changes that may give us more informative error messages when a time out occurs.
see bug #87144. It seems that firewalls can cause problems for the debugger. Still investigating. Does disabling your firewall make a difference?
*** This bug has been marked as a duplicate of 83937 ***
*** Bug 91017 has been marked as a duplicate of this bug. ***
