Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 81653 - org.eclipse.jdi.TimeoutException occurred retrieving frame count.
Summary: org.eclipse.jdi.TimeoutException occurred retrieving frame count.
Status: RESOLVED DUPLICATE of bug 83937
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.0.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-20 11:03 EST by colin Wyatt CLA
Modified: 2005-04-04 16:49 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description colin Wyatt CLA 2004-12-20 11:03:39 EST
When dubugging code and stopping on a break point I get the following error 
when attempting to resume program execution: 

org.eclipse.debug.core.DebugException[5010]: org.eclipse.jdi.TimeoutException
at org.eclipse.jdi.internal.connect.PacketReceiveManager.getReply
(PacketReceiveManager.java:149)
at org.eclipse.jdi.internal.connect.PacketReceiveManager.getReply
(PacketReceiveManager.java:158)
at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:173)
at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:191)
at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:206)
at org.eclipse.jdi.internal.ThreadReferenceImpl.frameCount
(ThreadReferenceImpl.java:147)
at org.eclipse.jdt.internal.debug.core.model.JDIThread.getUnderlyingFrameCount
(JDIThread.java:629)
at org.eclipse.jdt.internal.debug.core.model.JDIThread.computeStackFrames
(JDIThread.java:416)
at org.eclipse.jdt.internal.debug.core.model.JDIThread.computeStackFrames
(JDIThread.java:515)
at org.eclipse.jdt.internal.debug.core.model.JDIThread.getStackFrames
(JDIThread.java:393)
at 
org.eclipse.debug.internal.ui.views.launch.LaunchViewContentProvider.getChildren
(LaunchViewContentProvider.java:41)
at org.eclipse.jface.viewers.AbstractTreeViewer.getRawChildren
(AbstractTreeViewer.java:708)
at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren
(StructuredViewer.java:477)
at org.eclipse.jface.viewers.StructuredViewer.getSortedChildren
(StructuredViewer.java:585)
at org.eclipse.jface.viewers.AbstractTreeViewer$1.run
(AbstractTreeViewer.java:359)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren
(AbstractTreeViewer.java:342)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalExpand
(AbstractTreeViewer.java:878)
at org.eclipse.jface.viewers.AbstractTreeViewer.setSelectionToWidget
(AbstractTreeViewer.java:1357)
at org.eclipse.jface.viewers.StructuredViewer.setSelectionToWidget
(StructuredViewer.java:1133)
at org.eclipse.jface.viewers.StructuredViewer.preservingSelection
(StructuredViewer.java:869)
at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:922)
at org.eclipse.debug.internal.ui.views.launch.LaunchViewer.refresh
(LaunchViewer.java:110)
at org.eclipse.debug.internal.ui.views.AbstractDebugEventHandler.refresh
(AbstractDebugEventHandler.java:136)
at 
org.eclipse.debug.internal.ui.views.launch.LaunchViewEventHandler.doHandleResume
Event(LaunchViewEventHandler.java:139)
at 
org.eclipse.debug.internal.ui.views.launch.LaunchViewEventHandler.doHandleDebugE
vents(LaunchViewEventHandler.java:96)
at org.eclipse.debug.internal.ui.views.AbstractDebugEventHandler$1.run
(AbstractDebugEventHandler.java:70)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:106)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:2749)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2434)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:668)
at org.eclipse.jface.window.Window.open(Window.java:648)
at org.eclipse.jface.dialogs.ErrorDialog.open(ErrorDialog.java:257)
at org.eclipse.jface.dialogs.ErrorDialog.openError(ErrorDialog.java:319)
at org.eclipse.jface.dialogs.ErrorDialog.openError(ErrorDialog.java:285)
at org.eclipse.debug.internal.ui.DebugUIPlugin.errorDialog
(DebugUIPlugin.java:451)
at org.eclipse.debug.internal.ui.actions.AbstractDebugActionDelegate.run
(AbstractDebugActionDelegate.java:114)
at 
org.eclipse.debug.internal.ui.actions.AbstractListenerActionDelegate.runWithEven
t(AbstractListenerActionDelegate.java:112)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:266)
at org.eclipse.ui.internal.WWinPluginAction.runWithEvent
(WWinPluginAction.java:206)
at org.eclipse.ui.commands.ActionHandler.execute(ActionHandler.java:143)
at org.eclipse.ui.internal.commands.Command.execute(Command.java:132)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand
(WorkbenchKeyboard.java:453)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press
(WorkbenchKeyboard.java:871)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent
(WorkbenchKeyboard.java:912)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings
(WorkbenchKeyboard.java:530)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$2
(WorkbenchKeyboard.java:478)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard$1.handleEvent
(WorkbenchKeyboard.java:243)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
at org.eclipse.swt.widgets.Display.filterEvent(Display.java:740)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:795)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:820)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:805)
at org.eclipse.swt.widgets.Control.sendKeyEvent(Control.java:1734)
at org.eclipse.swt.widgets.Control.sendKeyEvent(Control.java:1730)
at org.eclipse.swt.widgets.Control.WM_KEYDOWN(Control.java:3517)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:2997)
at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1391)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:3338)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:1473)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2429)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1377)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1348)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:254)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:141)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:96)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run
(PlatformActivator.java:335)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:273)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.eclipse.core.launcher.Main.basicRun(Main.java:185)
at org.eclipse.core.launcher.Main.run(Main.java:704)
at org.eclipse.core.launcher.Main.main(Main.java:688)

It doesn't happen all the time, but today is particularly bad, and is really 
stopping me from getting on with my work.

I'm using j2sdk1.4.2_05 to run Eclipse, and jdk1.3.1_02 for the application.

Any help you can give will be appreciated.

Regards

Colin Wyatt
Comment 1 Darin Wright CLA 2004-12-20 11:06:16 EST
Try increasing the communication timeout preference on the Java > Debug 
preference page.
Comment 2 colin Wyatt CLA 2004-12-21 05:59:48 EST
Thanks for you're swift reply. This appears to have resolved the situation. Is 
there an upper limit to debugger timeout value that can be set.
Comment 3 Darin Wright CLA 2004-12-21 09:24:11 EST
There is no upper limit to the timeout value that can be set. However, unless 
the connection you are debugging over is consistently slow, the value should 
not need to be increased much. 

Re-opening to mark as "works for me" (we din't fix anything).
Comment 4 Darin Wright CLA 2004-12-21 09:24:26 EST
Marking as "works for me".
Comment 5 colin Wyatt CLA 2005-01-14 08:00:03 EST
I am still getting timeout problems I think, although it's hard to tell, as the 
application hangs, and no logs are being written. However, the problem occurs 
when trying to debug an application. I've tried increasing the timeout threshold
without any success. I can't understand why I should be getting timeout 
problems at all, as everything to do with what I'm working on is situated 
locally on my m/c. This problem is making it impossible to do any work. Could 
you please advise of any other reasons which might cause this problem to occur.

Regards

Colin Wyatt
Comment 6 Darin Wright CLA 2005-01-14 08:13:40 EST
What VM & version are you using to debug your application?
Comment 7 colin Wyatt CLA 2005-01-14 08:20:31 EST
I'm using j2sdk1.4.2_05 to run Eclipse, and jdk1.3.1_02 for the application.

Comment 8 Darin Wright CLA 2005-01-14 08:27:01 EST
Can you trying a newer version of 1.3.1? For example, I have a newer vesrion = 
1.3.1_13.
Comment 9 Darin Wright CLA 2005-01-31 09:15:25 EST
Any luck with a newer JVM?
Comment 10 Darin Wright CLA 2005-03-09 11:29:31 EST
See bug 87144. Do you have a firewall running? If you disable the firewall, 
does the problem stop?
Comment 11 Darin Wright CLA 2005-03-30 18:02:01 EST
Anymore progress on this one?
Comment 12 Darin Wright CLA 2005-04-04 16:49:05 EDT

*** This bug has been marked as a duplicate of 83937 ***