Note, I'm also running a patched version of the davex stack, on the client of course, that allows for the number of http connections created to be configured. Previously, we had witnessed only two connections, and it was causing a bottleneck. Could we have uncovered a concurrency issue with the webdav server now that we're hitting it with more than two connections at once?
On Mon, Jun 27, 2011 at 12:54 PM, ChadDavis <[email protected]> wrote: > I'm not making much headway in interpreting this error. My client app > connects to the repo via davex. I've actually got spinning request > threads on the client app, so it kind of makes sense that they aren't > "closing sessions". However, I can't find a reason for this in my > code. Can someone explain to me what the first two lines about the > "references" means? > > > 2011-06-27 07:23:51.011 ERROR [qtp1530970753-15] > JCRWebdavServer.java:210 Failed to add reference to session. No entry > in cache found. > 2011-06-27 07:23:51.012 ERROR [qtp1530970753-15] > JCRWebdavServer.java:246 Failed to remove reference from session. No > entry in cache found. > 2011-06-27 07:23:53.160 WARN [Finalizer] SessionImpl.java:1261 > Unclosed session detected. The session was opened here: > java.lang.Exception: Stack Trace > at org.apache.jackrabbit.core.SessionImpl.<init>(SessionImpl.java:217) > ~[jackrabbit-core-2.2.5.jar:2.2.5] > at org.apache.jackrabbit.core.SessionImpl.<init>(SessionImpl.java:234) > ~[jackrabbit-core-2.2.5.jar:2.2.5] > at > org.apache.jackrabbit.core.XASessionImpl.<init>(XASessionImpl.java:99) > ~[jackrabbit-core-2.2.5.jar:2.2.5] > at > org.apache.jackrabbit.core.RepositoryImpl.createSessionInstance(RepositoryImpl.java:1578) > ~[jackrabbit-core-2.2.5.jar:2.2.5] > at > org.apache.jackrabbit.core.RepositoryImpl.createSession(RepositoryImpl.java:947) > ~[jackrabbit-core-2.2.5.jar:2.2.5] > at > org.apache.jackrabbit.core.RepositoryImpl.login(RepositoryImpl.java:1477) > ~[jackrabbit-core-2.2.5.jar:2.2.5] > at > org.apache.jackrabbit.server.SessionProviderImpl.getSession(SessionProviderImpl.java:55) > ~[jackrabbit-jcr-server-2.2.5.jar:2.2.5] > at > org.apache.jackrabbit.server.jcr.JCRWebdavServer$SessionCache.getRepositorySession(JCRWebdavServer.java:286) > ~[jackrabbit-jcr-server-2.2.5.jar:2.2.5] > at > org.apache.jackrabbit.server.jcr.JCRWebdavServer$SessionCache.get(JCRWebdavServer.java:187) > ~[jackrabbit-jcr-server-2.2.5.jar:2.2.5] > at > org.apache.jackrabbit.server.jcr.JCRWebdavServer$SessionCache.access$100(JCRWebdavServer.java:143) > ~[jackrabbit-jcr-server-2.2.5.jar:2.2.5] > at > org.apache.jackrabbit.server.jcr.JCRWebdavServer.attachSession(JCRWebdavServer.java:81) > ~[jackrabbit-jcr-server-2.2.5.jar:2.2.5] > at > org.apache.jackrabbit.webdav.server.AbstractWebdavServlet.service(AbstractWebdavServlet.java:191) > ~[jackrabbit-webdav-2.2.5.jar:2.2.5] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > ~[servlet-api-2.5.jar:2.5] >
