[
https://issues.apache.org/jira/browse/TAPESTRY-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628983#action_12628983
]
Francois Armand commented on TAPESTRY-2561:
-------------------------------------------
We have done some load test on our application, and one time, we get the
deadlock, so I will try to explain what we did.
* if I start the application, and use it a little (even if I don't go
everywhere), everything is ok : on a load test, we were able to let the server
run under the load of 4 computers, 25 jmeter threads by computer during several
hours, without the deadlock.
* if I start the application and immediately launch the jmeter test with say 25
threads, the application goes to the deadlock.
I tried to reproduce this bug in a demo application, but did not succeed. It
seems that trivial application run just fine, even with a bunch of thread
launch at once.
> 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]
