[jboss-jira] [JBoss JIRA] (JBWEB-222) thread hang at org.apache.naming.resources.ProxyDirContext.cacheLoad(..)

[Jean-Frederic Clere (JIRA)]

     [ https://issues.jboss.org/browse/JBWEB-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Frederic Clere resolved JBWEB-222.
---------------------------------------

    Resolution: Done

    
> thread hang at org.apache.naming.resources.ProxyDirContext.cacheLoad(..)
> ------------------------------------------------------------------------
>
>                 Key: JBWEB-222
>                 URL: https://issues.jboss.org/browse/JBWEB-222
>             Project: JBoss Web
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Tomcat
>    Affects Versions: JBossWeb-7.0.1.GA 
>         Environment: OpenShift Express
>            Reporter: William DeCoste
>            Assignee: Remy Maucherat
>             Fix For: JBossWeb-7.0.9.GA
>
>         Attachments: stacktrace.txt, threaddump.txt
>
>
> OpenShift Express user reported their gitblit app hit the limit of 64 threads although the app should not be thread-intensive. The attached stacktrace and thread dump show 63 BLOCKED threads at at org.apache.naming.resources.ProxyDirContext.cacheLoad(..) and 1 RUNNABLE at org.apache.naming.resources.ResourceCache.allocate(..). The attached stacktrace shows an exception in the latter thread.
> NOTE: Express runs with the LOW_MEMORY setting enabled.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira