This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 59553 - Java Navigator forever in Please wait... state
Summary: Java Navigator forever in Please wait... state
Status: RESOLVED WORKSFORME
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-02 14:42 UTC by Antonin Nebuzelsky
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Thread Dump (12.35 KB, text/plain)
2005-06-02 14:42 UTC, Antonin Nebuzelsky 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Antonin Nebuzelsky 2005-06-02 14:42:06 UTC 
In a certain unknown moment Navigator starts displaying Please wait... and never
actually completes populating its contents. Navigator forever stays displaying
Please wait. I don't know when exactly this happens but I have encountered it
several times already.

I am at least attaching a thread dump. Maybe something interesting can be seen
in there...
Comment 1 Antonin Nebuzelsky 2005-06-02 14:42:38 UTC 
Created attachment 22452 [details]
Thread Dump
Comment 2 David Simonek 2005-08-05 15:40:36 UTC 
Yes, thread dump is interesting, it shows that Nvaigator just waits for MDR
scan, as several other threads. But it seems that MDR is in some bad state, and
JMManager.waitScanFinished never returns, so passign to java guys.

Btw, I came to this state once also, and I remember a lot of MDR related
exceptions to be thrown.
Comment 3 Tomas Hurka 2005-08-05 16:47:25 UTC 
Please attach also ide.log.
Any exceptions in ide.log?
Comment 4 Martin Matula 2005-08-18 16:38:39 UTC 
Not enough info to find out what's going on. Not even a build number.
messages.log would be helpful - this is likely caused by some exception that
happened before.
Comment 5 Milan Kubec 2005-11-01 12:26:26 UTC 
Tondo, please could you provide requested information? Thanks.
Comment 6 Antonin Nebuzelsky 2005-11-01 12:42:02 UTC 
I don't remember I would see the problem recently. So I cannot give more details.

I don't have the userdir from Jun/2 anymore. I just can say I was using the
latest available daily build at that time.

Feel free to close. I'd reopen if I see it again...
Comment 7 Milan Kubec 2005-11-15 15:44:50 UTC 
Closing as Tonda suggested.