[
https://issues.apache.org/jira/browse/TAPESTRY-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAPESTRY-2561.
------------------------------------------
Resolution: Fixed
I think I've nailed it. The trick is to ensure that the context class loader's
monitor is locked before the component class loader. Also, reduced the
synchronization inside ModuleImpl, to alllow many readers/one writer when
accessing service proxies.
Those who have been affected by the bug should retest with the next snapshot
(i.e., available on monday sep 8) to see if they can reproduce the problem.
> 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]
