[TAP5-1650] On a cold start with a large number of incoming requests, Tapestry can deadlock inside PlasticClassLoader/PlasticClassPool

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 5.3
• Fix Version/s: 5.3
• Component/s: plastic
• Labels: deadlock performance
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 14/Sep/11 17:06
• Updated: 30/Mar/17 06:08
• Resolved: 17/Oct/11 22:22

Description

Discovered during load testing; the scenario is a cold start for the application then hitting it with large numbers of concurrent requests with no ramp up. The deadlocks involve two methods:

PlasticClassLoader.loadClass()
PlasticClassPool.getClassInstantiator()

A proper solution would to make these methods share a single explicit Lock, rather than be synchronized.

Issue Links

• is related to: TAP5-2546 Parallel class loading