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 81771 - TooManyListenersException
Summary: TooManyListenersException
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Navigation (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: David Simonek
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2006-08-03 02:33 UTC by Jesse Glick
Modified: 2006-11-20 11:55 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Stack trace (556 bytes, text/plain)
2006-08-03 02:33 UTC, Jesse Glick 		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 Jesse Glick 2006-08-03 02:33:14 UTC 
Dev build, JDK 5. Just made a new j2seproject w/ main class, added a println,
F6. Waited for CP scanning to complete, project ran, got this exception on console.
Comment 1 Jesse Glick 2006-08-03 02:33:44 UTC 
Created attachment 32475 [details]
Stack trace
Comment 2 Peter Pis 2006-08-22 15:33:45 UTC 
Happens in NB 5.5 too.
Comment 3 Peter Pis 2006-08-22 15:34:22 UTC 
Product Version         = NetBeans 5.5 Dev (Build 060822)
Operating System        = Windows XP version 5.1 running on x86
Java; VM; Vendor; Home  = 1.5.0_07; Java HotSpot(TM) Client VM 1.5.0_07-b03; Sun
Microsystems Inc.
Comment 4 David Simonek 2006-08-22 15:49:35 UTC 
OK ppis, but any reproductible scenario? I'm not able to fix if it is just
random, as it's in complicated code written by someone else.
Comment 5 Peter Pis 2006-08-22 16:09:15 UTC 
I don't have exact repro case. It's random. It was thrown while automatic test
had been performed.

Steps of test: (j2se project)
1. Check project from CVS repository and open it. (working location 1)
2. Modify sources and close project. (2 files)
3. Check the same project from CVS repository and open it. (but into working
location 2) 
4. Modify the same sources at the same lines (to ensure conflict in next step)
and commit them. Close project.
5. Open the project from working location 1 and update it, conficts occur. 

Exception is randomly thrown.
Comment 6 Jesse Glick 2006-08-22 20:55:20 UTC 
I've seen this several times in commit validation, IIRC. If you don't know why
it happens and can't find out and believe it's harmless, at least comment out
the printStackTrace().
Comment 7 Petr Hrebejk 2006-11-20 11:55:39 UTC 
The class no longer exists.