Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
4.1.5
-
None
-
None
-
JDK 1.5.0_14 64 bit, Tomcat 5.5.26
Description
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
Attachments
Attachments
Issue Links
- is related to
-
TAPESTRY-2530 Possible performance bottleneck in PageSource.makeObject()
- Resolved