[
https://issues.apache.org/jira/browse/TAPESTRY-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620790#action_12620790
]
Howard M. Lewis Ship commented on TAPESTRY-2561:
------------------------------------------------
I've implemented the global MUTEX.
It is used for module class instantation, service proxy creation as well as
serializing loading/transformation of component classes. On an application
that is heavily accessed immediately upon startup, we should see one thread
largely monopolize the creation of new service proxies and component class
loading while other threads block. This is neither a good thing nor a bad
thing.
> 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
> 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]
