[
https://issues.apache.org/jira/browse/TAPESTRY-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629001#action_12629001
]
Howard M. Lewis Ship commented on TAPESTRY-2561:
------------------------------------------------
First, I'm able to reliably reproduce a deadlock (hopefully, the only deadlock)
using JMeter on my MacBook Pro. That's great, since I don't have to try to
reproduce some of these environments.
I've been running experiments and have found that the right solution is:
1) The PackageAwareLoader (the loader for component classes) must synchronize
its activity against the parent class loader (the context class loader).
2) The global mutex should be eliminated, it just causes deadlocks.
With these changes in place, I can no longer reproduce the deadlock.
> Rapidly refreshing a page, even the same page, can cause a deadlock related
> to class loading
> --------------------------------------------------------------------------------------------
>
> 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
> Priority: Blocker
> Fix For: 5.0.15
>
> 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]
