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 59852 - Concurrency issues related to profiler own use of some classes as a result of classLoadHook
Summary: Concurrency issues related to profiler own use of some classes as a result of...
Status: CLOSED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: All All
: P4 blocker (vote)
Assignee: iformanek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-10 16:19 UTC by iformanek
Modified: 2007-02-12 21:58 UTC (History)
0 users

See Also:
Issue Type: TASK
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description iformanek 2005-06-10 16:19:49 UTC
The tomcat startup hangs if CPU profiling (Entire app) is used and tomcat runs 
on Tiger or Mustang.
Comment 1 iformanek 2005-06-10 16:24:43 UTC
The problem is caused by a concurrency issue between tool and client.

as part of processing class loaded command from agent, the tool asks the agent 
for defining class loader. Processing the request on the agent side leads to 
classLoadHook being called for class java.util.AbstractList$Itr, which cannot 
proceed because the serialClientOperationsLock is being held by the previous 
classLoadHook invocation from the main thread.

For now, resolving this for this special case by preloading the 
java.util.AbstractList$Itr class in the agent. More systemic solution should 
probably be used to address this, but for now lowering the priority on this 
issue to P4, as the primary cause is resolved.
Comment 2 iformanek 2005-06-15 10:50:14 UTC
Changing to task, planning for M8
Comment 3 iformanek 2005-08-15 11:49:27 UTC
This has been sufficiently addressed in M8, closing
Comment 4 ehucka 2006-10-09 12:08:41 UTC
Verification of old issues.
Comment 5 Alexander Kouznetsov 2007-02-12 21:58:19 UTC
Closing old issues.