[
https://issues.apache.org/jira/browse/TAP5-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639211#action_12639211
]
Howard M. Lewis Ship commented on TAP5-248:
-------------------------------------------
Looking at the stack traces, it looks normal; one thread has acquired the write
lock on the concurrent barrier, and has released it and is attempting to
re-acquire the read lock. All other threads are blocked waiting for the read
lock. This points towards the JDK bug, in that nobody should have the write
lock, so there shouldn't be a deadlock waiting for the read lock.
> Page initialization deadlock
> ----------------------------
>
> Key: TAP5-248
> URL: https://issues.apache.org/jira/browse/TAP5-248
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.15
> Reporter: Henning Petersen
> Attachments: thread+dump.txt
>
>
> I have a deadlock in my application related to class loading. When I don't
> warm up the app by viewing page after page, but click on pages in my menu
> randomly without giving them time to initialize, the application locks up.
> I'm attaching a thread dump. Everything halts in
> org.apache.tapestry5.ioc.internal.util.ConcurrentBarrier.withRead(ConcurrentBarrier.java:73).
> This might be related to TAPESTRY-2561, as the symptoms are the same.
--
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]
