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 30612 - Deadlock in on startup using Optimizeit
Summary: Deadlock in on startup using Optimizeit
Status: CLOSED DUPLICATE of bug 30129
Alias: None
Product: platform
Classification: Unclassified
Component: Filesystems (show other bugs)
Version: 3.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: rmatous
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-03 18:03 UTC by Michael Ottati
Modified: 2008-12-22 19:30 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Full stack trace of deadlock. (16.70 KB, text/plain)
2003-02-03 18:04 UTC, Michael Ottati 		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 Michael Ottati 2003-02-03 18:03:52 UTC 
This bug only occurs when attempting to run under 
Optimizeit. It does appear reproducable and it looks like 
the stack trace that is reported in IZ 30153 also.

This bug occurs with the following configuration.

S1S + Qbuild of 2003-01-22

I have encountered this deadlock every time I have 
attempted to run S1S under Optimizeit using this Q build. 
I have used Optimizeit on prior build but not sure how 
long ago. I think 2 Q builds back worked, not sure about 
previous Q build from Jan 22.

One other factor which may be interesting, I have 
installed the "test tools" module from autoupdate and 
overlayed the following files in modules/ext of my user 
directory.

jelly-nb.jar
jelly2-nb.jar
jemmy.jar
Comment 1 Michael Ottati 2003-02-03 18:04:32 UTC 
Created attachment 8769 [details]
Full stack trace of deadlock.
Comment 2 pzajac 2003-02-04 08:37:59 UTC 
duplicate and fixed.

*** This issue has been marked as a duplicate of 30129 ***
Comment 3 Marian Mirilovic 2003-07-22 15:32:10 UTC 
verified, closed - it's duplicate.