[
https://issues.apache.org/jira/browse/TAPESTRY-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620781#action_12620781
]
Howard M. Lewis Ship commented on TAPESTRY-2561:
------------------------------------------------
>From what I can tell, this occurs because more than one thread is attempting
>to define a class at the same time.
In both examples that we've gotten, one thread is defining a new class on the
context class loader (i.e., defining service proxies, etc.) while another is
defining a new class on the component class loader (a child of the context
class loader). You wouldn't think they interfere, but it appears that adding a
class on the child affects the parent. I still don't get why this is a
deadlock however.
I'm beginning to think there needs to be a global mutex for this purpose
> Deadlock when double clicking a pagelink
> ----------------------------------------
>
> Key: TAPESTRY-2561
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2561
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.14
> Environment: Mac pro, OS Version: Mac OS X 10.5.4 (9E17)
> Java HotSpot(TM) Client VM (1.5.0_13-119 mixed mode,
> sharing)
> Reporter: Steven Woolley
> Assignee: Howard M. Lewis Ship
> Attachments: full thread dump deadlock.txt
>
>
> It was triggered by (accidentally) double clicking a pagelink ;)
> Unfortunately, can't quite repeat it... at least not clicking with a mouse...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
