[jboss-jira] [JBoss JIRA] (JBWEB-223) thread hang at org.apache.naming.resources.ResourceCache.allocate(..)

[Jean-Frederic Clere (JIRA)]

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

Jean-Frederic Clere updated JBWEB-223:
--------------------------------------

      Fix Version/s: JBossWeb-7.0.9.GA
    Forum Reference: https://www.redhat.com/openshift/community/forums/express/how-to-see-jboss-log-output  (was: https://www.redhat.com/openshift/community/forums/express/how-to-see-jboss-log-output)

    
> thread hang at org.apache.naming.resources.ResourceCache.allocate(..)
> ---------------------------------------------------------------------
>
>                 Key: JBWEB-223
>                 URL: https://issues.jboss.org/browse/JBWEB-223
>             Project: JBoss Web
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Tomcat
>         Environment: OpenShift Express
>            Reporter: William DeCoste
>            Assignee: Remy Maucherat
>             Fix For: JBossWeb-7.0.9.GA
>
>         Attachments: stdout.log
>
>
> OpenShift Express user reported their wicket app was returning a proxy error. The root cause is a hang at ServletContext.getResource(..) that causes a timeout and the proxy error. The attached stack trace shows a RUNNABLE thread hung at org.apache.naming.resources.ResourceCache.allocate(..).
> NOTE: Express runs with the LOW_MEMORY setting enabled. if the LOW_MEMORT setting is disabled, the hang does not occur and the app behaves as expected.

--
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