You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Stefan Koelmann (JIRA)" <de...@tapestry.apache.org> on 2008/07/21 14:37:31 UTC
[jira] Updated: (TAPESTRY-2530) Possible Performance Bottleneck in
PageSource.makeObject()
[ https://issues.apache.org/jira/browse/TAPESTRY-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Koelmann updated TAPESTRY-2530:
--------------------------------------
Attachment: threaddump.zip
Thread dump illustrating the problem with the locked threads.
> Possible Performance Bottleneck in PageSource.makeObject()
> ----------------------------------------------------------
>
> Key: TAPESTRY-2530
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2530
> Project: Tapestry
> Issue Type: Bug
> Affects Versions: 4.1.2
> Environment: JDK 1.5.0_14 64 bit, Tomcat 5.5.26
> Reporter: Stefan Koelmann
> Priority: Critical
> Attachments: threaddump.zip
>
>
> We recently migrated from Tapestry 3 to Tapestry 4.1.2 and are experiencing severe performance problems with mediocre load.
> At some point our servers start creating new threads until the Tomcat reaches the maximum of 500 live threads. When examining the thread dump, we find one thread holding a lock at the GenericKeyedObjectPool, while hundreds of other threads are waiting to aquire just this lock.
> It seems the locking thread is constructig a page from a synchronized context and needs some time to do so, and this leads to the complete application locking up in no time. See the threaddump attached.
> We already tried an upgrade to commons-pool 1.4 with no real effect.
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org