[ 
https://issues.apache.org/jira/browse/TAPESTRY-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632596#action_12632596
 ] 

jens breitenstein commented on TAPESTRY-2561:
---------------------------------------------

currently this deadlock appears frequently when we start a tomcat under heavy 
load (let me guess in 95% of the time the deadlock occurs in  5% T5 starts 
correctly). Am I right, that the error occurs because the pages/components byte 
code manipulation is defered to first access of a particular page to minimize 
the startup time? If so what about just initializing all pages/components while 
starting up? ok, the startup time will increase but for production it plays no 
role if startup takes 30 sec or 5 min, right? this will be different for 
development I know, but when starting a TC locally there will be no heavy load 
so chances to get trapped by this error should be considerably low. Furthermore 
if T5 initializes all pages we will catch page errors immediately on startup 
instead of finding them "accidentally when clicking through the app" (but this 
is a different topic). Nevertheless I fear the frameset problem mentioned 
before by Jun Tsai is different from our's

> 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]

Reply via email to