Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
4.1.2, 4.1.5
-
None
-
None
-
JDK 1.5.0_14 64 bit, Tomcat 5.5.26
Description
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.
Attachments
Attachments
Issue Links
- is related to
-
TAPESTRY-2382 Possible deadlock in ExpressionCacheImpl (on _lock instance)
- Resolved
- relates to
-
TAPESTRY-2604 Synchronization Bottleneck in ComponentConstructorFactoryImpl
- Open