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

[William DeCoste (JIRA)]

William DeCoste created JBWEB-223:
-------------------------------------

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