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/08/19 16:33:44 UTC
[jira] Created: (TAPESTRY-2604) Synchronization Bottleneck in
ComponentConstructorFactoryImpl
Synchronization Bottleneck in ComponentConstructorFactoryImpl
-------------------------------------------------------------
Key: TAPESTRY-2604
URL: https://issues.apache.org/jira/browse/TAPESTRY-2604
Project: Tapestry
Issue Type: Bug
Components: Framework
Affects Versions: 4.1.5
Environment: JDK 1.5.0_14 64 bit, Tomcat 5.5.26
Reporter: Stefan Koelmann
Attachments: ThreadDumps.zip
After fixing TAPESTRY-2530, it seems we got another performance bottleneck during page rendering: Under rather heavy load a lot of threads get stuck at ComponentConstructorFactoryImpl.getComponentConstructor. It seems the lock is held to long; a lot of threads gets queued and the application stops responding properly.
I attached two threaddumps showing the problem. A possible solution could be to split the synchronization lock; guarding only the private field _cachedConstructors and not the construction of a new constructors, if this is necessary.
Thanks for your help,
Stefan
--
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
[jira] Updated: (TAPESTRY-2604) Synchronization Bottleneck in
ComponentConstructorFactoryImpl
Posted by "Stefan Koelmann (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Koelmann updated TAPESTRY-2604:
--------------------------------------
Attachment: ThreadDumps.zip
> Synchronization Bottleneck in ComponentConstructorFactoryImpl
> -------------------------------------------------------------
>
> Key: TAPESTRY-2604
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2604
> Project: Tapestry
> Issue Type: Bug
> Components: Framework
> Affects Versions: 4.1.5
> Environment: JDK 1.5.0_14 64 bit, Tomcat 5.5.26
> Reporter: Stefan Koelmann
> Attachments: ThreadDumps.zip
>
>
> After fixing TAPESTRY-2530, it seems we got another performance bottleneck during page rendering: Under rather heavy load a lot of threads get stuck at ComponentConstructorFactoryImpl.getComponentConstructor. It seems the lock is held to long; a lot of threads gets queued and the application stops responding properly.
> I attached two threaddumps showing the problem. A possible solution could be to split the synchronization lock; guarding only the private field _cachedConstructors and not the construction of a new constructors, if this is necessary.
> Thanks for your help,
> Stefan
--
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