Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 207574

Summary:

[model] Retrieval of remote javadocs crashes if user has disconnected

Product:

[Eclipse Project] JDT

Reporter:

Paul E. Keyser <rolarenfan>

Component:

Core

Assignee:

JDT-Core-Inbox <jdt-core-inbox>

Status:

CLOSED WONTFIX

QA Contact:

Severity:

normal

Priority:

CC:

jerome_lanneluc

Version:

3.3

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

stalebug

Attachments:

Description	Flags
.log file showing the crashes	none

Description Paul E. Keyser

2007-10-26 09:38:39 EDT

Build ID: I20070621-1340

Steps To Reproduce:
1. Run Eclipse, have Java files open, be connected to the net, have opened javadoc for some java.lang method/class or the like; 
2. While Eclipse is running, suspend (Windows: "Stand By"); 
3. Un-suspend, in a place where you are not plugged in and there is no wireless; 
4. Return to the still running Eclipse, and try to open the popup javadoc for a java.lang method or class or the like
5. Get call stacks as in .log file to be attached


More information:
I'm only reporting this for Windoze; no clue if it happens on other platforms. 

Admittedly an edge-case, but should not be handled with an endless stream of exceptions filling up the log.

Comment 1 Paul E. Keyser

2007-10-26 09:39:35 EDT

Created attachment 81261 [details]
.log file showing the crashes

Comment 2 Jerome Lanneluc

2007-10-30 08:17:13 EDT

Might be a dup of bug 206177

Comment 3 Eclipse Genie

2019-12-28 15:38:29 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.