Web-explorer is leaking connections if running on AS5
Hello ModeShapers,
In my environment MS is running on a AS5 in an ear containing the RA, DS and web-explorer (as proposed somewhere in the documention). I can access the web-explorer via JNDI-URL.
But though the login is successful I still get the following stacktrace:
{noformat}
10:13:59,167 ERROR [STDERR] org.modeshape.web.jcr.NoSuchRepositoryException: No repository 'java:dms/datastore' was found.
10:13:59,168 ERROR [STDERR] at org.modeshape.web.jcr.RepositoryManager.getRepository(RepositoryManager.java:142)
10:13:59,168 ERROR [STDERR] at org.modeshape.web.server.JcrServiceImpl.login(JcrServiceImpl.java:93)
10:13:59,168 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
10:13:59,168 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
10:13:59,168 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
10:13:59,171 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:597)
10:13:59,171 ERROR [STDERR] at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:561)
10:13:59,171 ERROR [STDERR] at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:208)
10:13:59,171 ERROR [STDERR] at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:248)
10:13:59,171 ERROR [STDERR] at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)
10:13:59,171 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
10:13:59,171 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
10:13:59,171 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
10:13:59,171 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
10:13:59,171 ERROR [STDERR] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
10:13:59,171 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
10:13:59,171 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
10:13:59,172 ERROR [STDERR] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
10:13:59,172 ERROR [STDERR] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
10:13:59,172 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183)
10:13:59,172 ERROR [STDERR] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95)
10:13:59,172 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
10:13:59,172 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
10:13:59,172 ERROR [STDERR] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
10:13:59,172 ERROR [STDERR] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
10:13:59,172 ERROR [STDERR] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
10:13:59,172 ERROR [STDERR] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
10:13:59,172 ERROR [STDERR] at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.internalProcess(ActiveRequestResponseCacheValve.java:74)
10:13:59,172 ERROR [STDERR] at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:47)
10:13:59,172 ERROR [STDERR] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
10:13:59,172 ERROR [STDERR] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
10:13:59,172 ERROR [STDERR] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:599)
10:13:59,173 ERROR [STDERR] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:451)
10:13:59,173 ERROR [STDERR] at java.lang.Thread.run(Thread.java:662)
{noformat}
Now while this error could be ignored the following info is much more interesting:
{noformat}
10:13:59,183 INFO [CachedConnectionManager] Could not find a close method on alleged connection objects. Please close your own connections.
{noformat}
What does that mean? Debugging shows that the CachedConnectionManager tries to close a non-closed JcrSessionHandle. But it cannot as this Class does not provide a close()-Method.
Now the ugly part is, that login to the explorer multiple times will eat up all the connection from the pool. To workaround the issue I can add the close()-Method but I think it is better to find the root cause.
Any ideas?
Thanks, Niels
