[ https://issues.apache.org/jira/browse/TAP5-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104908#comment-13104908 ]
Hudson commented on TAP5-1650: ------------------------------ Integrated in tapestry-trunk-freestyle #521 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/521/]) TAP5-1650: On a cold start with a large number of incoming requests, Tapestry can deadlock inside PlasticClassLoader/PlasticClassPool hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1170840 Files : * /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/ComponentInstantiatorSourceImpl.java > On a cold start with a large number of incoming requests, Tapestry can > deadlock inside PlasticClassLoader/PlasticClassPool > -------------------------------------------------------------------------------------------------------------------------- > > Key: TAP5-1650 > URL: https://issues.apache.org/jira/browse/TAP5-1650 > Project: Tapestry 5 > Issue Type: Bug > Components: plastic > Affects Versions: 5.3 > Reporter: Howard M. Lewis Ship > Assignee: Howard M. Lewis Ship > Priority: Critical > Labels: deadlock, performance > > 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. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira