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 56947 - Exceptions when running verifyer often
Summary: Exceptions when running verifyer often
Status: CLOSED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 8 (show other bugs)
Version: 4.x
Hardware: All All
: P3 blocker (vote)
Assignee: _ ludo
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-24 16:44 UTC by Jan Horvath
Modified: 2006-03-24 12:58 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
ArrayIndexOutOfBoundsException (1.90 KB, text/plain)
2005-03-24 16:44 UTC, Jan Horvath 		Details
NoSuchElementException (1.62 KB, text/plain)
2005-03-24 16:45 UTC, Jan Horvath 		Details
UndeclaredThrowableException (3.94 KB, text/plain)
2005-03-24 16:45 UTC, Jan Horvath 		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 Jan Horvath 2005-03-24 16:44:01 UTC 
build 200503231900

When running verifyer often I got NoSuchElementException, ArrayIndexOutOfBoundsException and than 
OutOfMemoryError
Comment 1 Jan Horvath 2005-03-24 16:44:26 UTC 
Created attachment 21114 [details]
ArrayIndexOutOfBoundsException
Comment 2 Jan Horvath 2005-03-24 16:45:03 UTC 
Created attachment 21115 [details]
NoSuchElementException
Comment 3 Jan Horvath 2005-03-24 16:45:34 UTC 
Created attachment 21116 [details]
UndeclaredThrowableException
Comment 4 _ ludo 2005-03-24 17:07:38 UTC 
Often: do you mean while a verifer task is running, you call a new one? or you
wait for the first one to finish before starting the other one?

What is the number for often? 2 or 100000?

Ludo
Comment 5 Jan Horvath 2005-03-24 17:54:55 UTC 
here is detailed description:
-I wait for the first one to finish, than start another.
-often = approximately 30 times
Comment 6 _ ludo 2005-03-29 02:26:39 UTC 
I've implemented the topcomponentClosed() hook to remove the possible listeners,
and nullify the panels, so the cleanup is ok I think.
Could not reproduce this state after more than 30 runs on my machine, so marking
as fixed.
Comment 7 Jan Horvath 2005-04-21 14:20:19 UTC 
v.