Description John Arthorne 2005-02-18 11:43:29 EST

Build: I20050215-2300

I frequently get messages like this in my log.  The term "Internal error" makes
it look scary, but it looks like a simple timeout (host VM not responding). 
Since this appears to be quite a frequent condition, and appears to cause no bad
side-effects, I recommend not logging them.  At the very least, don't log it as
"Internal error". These account for a good deal of the clutter in my log files:

!ENTRY org.eclipse.jdt.debug 4 120 2005-02-17 13:14:05.191
!MESSAGE Internal error logged from JDI Debug: 
!STACK 0
org.eclipse.jdi.TimeoutException: Timeout occurred while waiting for packet 32378
	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.status(ThreadReferenceImpl.java:345)
	at
org.eclipse.jdt.internal.debug.core.model.JDIThread.initialize(JDIThread.java:242)
	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.handleEvent(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:813)