https://issues.apache.org/bugzilla/show_bug.cgi?id=55533

            Bug ID: 55533
           Summary: ProxyDirContext throws null pointer exception on
                    reloaded context
           Product: Tomcat 7
           Version: 7.0.41
          Hardware: Macintosh
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Catalina
          Assignee: dev@tomcat.apache.org
          Reporter: mattha...@gmail.com

This looks to be a repeat of bug #24588, from some time ago...

I am actually able to reproduce this same issue consistently on tomcat 7.0.41
whenever I make a request on a reloaded context.

1) Deploy war (unpacked) onto tomcat (embedded,
org.apache.catalina.startup.Tomcat) with context set to reloadable
2) Make requests to webapp, works fine
3) Recompile war to trigger context reload
4) Each request to webapp gives this stacktrace

2013-09-06 22:32:35,093 [http-nio-8080-exec-8] ERROR
org.apache.coyote.http11.Http11NioProcessor - Error processing request
java.lang.NullPointerException
    at
org.apache.naming.resources.ProxyDirContext.cacheLoad(ProxyDirContext.java:1660)
    at
org.apache.naming.resources.ProxyDirContext.cacheLookup(ProxyDirContext.java:1536)
    at
org.apache.naming.resources.ProxyDirContext.lookup(ProxyDirContext.java:297)
    at
org.apache.tomcat.util.http.mapper.Mapper.internalMapWrapper(Mapper.java:1009)
    at org.apache.tomcat.util.http.mapper.Mapper.internalMap(Mapper.java:821)
    at org.apache.tomcat.util.http.mapper.Mapper.map(Mapper.java:684)
    at
org.apache.catalina.connector.CoyoteAdapter.postParseRequest(CoyoteAdapter.java:647)
    at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:403)
    at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1023)
    at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
    at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1686)
    at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:722)

Checked, and it is failing on the same line:
  int n = is.read(b, pos, length - pos);

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to