[Sakai Jira] Created: (KERN-1213) Stack trace in log file during sequential creation of users via curl

2 views
Skip to first unread message

Alan Berg (JIRA)

unread,
Oct 8, 2010, 7:35:31 AM10/8/10
to sakai-...@googlegroups.com
Stack trace in log file during sequential creation of users via curl
--------------------------------------------------------------------

Key: KERN-1213
URL: http://jira.sakaiproject.org/browse/KERN-1213
Project: Nakamura
Issue Type: Bug
Components: UserManagement - Jackrabbit
Affects Versions: 0.8
Environment: Hudson build - 476
Reporter: Alan Berg
Fix For: 0.9
Attachments: users.pl

This is a precautionary Jira. It may well be normal behaviour for the Exception to be generated.

Created 6000 users via CURL (script included),
Around 5500 users in, some warnings with stack traces were generated. This was not seen previously from Kernel builds a 4 days older (460)

Please comment.

08.10.2010 13:20:17.879 *WARN* [Finalizer] org.apache.jackrabbit.core.SessionImpl Unclosed session detected. The session was opened here: java.lang.Exception: Stack Trace
at org.apache.jackrabbit.core.SessionImpl.<init>(SessionImpl.java:237)
at org.apache.jackrabbit.core.SystemSession.<init>(SystemSession.java:76)
at org.apache.jackrabbit.core.SystemSession.create(SystemSession.java:64)
at org.apache.jackrabbit.core.DynamicSecurityManager.getAccessControlProvider(DynamicSecurityManager.java:564)
at org.apache.jackrabbit.core.DynamicSecurityManager.getAccessManager(DynamicSecurityManager.java:272)
at org.apache.jackrabbit.core.SessionImpl.createAccessManager(SessionImpl.java:373)
at org.apache.jackrabbit.core.SessionImpl.<init>(SessionImpl.java:290)
at org.apache.jackrabbit.core.SessionImpl.<init>(SessionImpl.java:259)
at org.apache.jackrabbit.core.XASessionImpl.<init>(XASessionImpl.java:107)
at org.apache.jackrabbit.core.RepositoryImpl.createSessionInstance(RepositoryImpl.java:1602)
at org.apache.jackrabbit.core.RepositoryImpl.createSession(RepositoryImpl.java:1010)
at org.apache.jackrabbit.core.RepositoryImpl.login(RepositoryImpl.java:1500)
at org.apache.sling.jcr.base.AbstractSlingRepository.login(AbstractSlingRepository.java:214)
at org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl.getResourceResolverInternal(JcrResourceResolverFactoryImpl.java:291)
at org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl.getResourceResolver(JcrResourceResolverFactoryImpl.java:262)
at org.apache.sling.auth.core.impl.SlingAuthenticator.getResolver(SlingAuthenticator.java:651)
at org.apache.sling.auth.core.impl.SlingAuthenticator.handleSecurity(SlingAuthenticator.java:402)
at org.apache.sling.engine.impl.SlingMainServlet.handleSecurity(SlingMainServlet.java:846)
at org.ops4j.pax.web.service.internal.HttpServiceServletHandler.handle(HttpServiceServletHandler.java:62)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.ops4j.pax.web.service.internal.HttpServiceContext.handle(HttpServiceContext.java:111)
at org.ops4j.pax.web.service.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:64)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:324)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:535)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:880)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520)


--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.sakaiproject.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira


Ian Boston (JIRA)

unread,
Oct 8, 2010, 8:20:31 AM10/8/10
to sakai-...@googlegroups.com

[ http://jira.sakaiproject.org/browse/KERN-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=110613#action_110613 ]

Ian Boston commented on KERN-1213:
----------------------------------

This happens when a session is not closed but cleaned up by the finalizer. Since there has been a lot of change in this area recently especially surrounding the eviction of sessions from the access control manager I would wait to let the dust settle and if this continues to happen then we will look at it. There is no real harm done by this, we put the diagnostic in to detect progamming issues. SO if you see this repeatedly from now onwards then please say, otherwise I think we can close this as a transient issue.

Ian Boston (JIRA)

unread,
Oct 11, 2010, 5:01:31 AM10/11/10
to sakai-...@googlegroups.com

[ http://jira.sakaiproject.org/browse/KERN-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ian Boston resolved KERN-1213.
------------------------------

Assignee: Ian Boston
Resolution: Fixed

I believe I have fixed this issue changing the way in which SystemSessions and AccessControlProviderHelpers are evicted from memory. Was happeing in large system me test, now not seen.

> Stack trace in log file during sequential creation of users via curl
> --------------------------------------------------------------------
>
> Key: KERN-1213
> URL: http://jira.sakaiproject.org/browse/KERN-1213
> Project: Nakamura
> Issue Type: Bug
> Components: UserManagement - Jackrabbit
> Affects Versions: 0.8
> Environment: Hudson build - 476
> Reporter: Alan Berg

> Assignee: Ian Boston

Alan Berg (JIRA)

unread,
Oct 11, 2010, 5:11:32 AM10/11/10
to sakai-...@googlegroups.com

[ http://jira.sakaiproject.org/browse/KERN-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=110747#action_110747 ]

Alan Berg commented on KERN-1213:
---------------------------------

Confirmed that for creating 6000 users no stacktrace was seen for build 487 - http://builds.sakaiproject.org:8080/job/Nakamura/

> Stack trace in log file during sequential creation of users via curl
> --------------------------------------------------------------------
>
> Key: KERN-1213
> URL: http://jira.sakaiproject.org/browse/KERN-1213
> Project: Nakamura
> Issue Type: Bug
> Components: UserManagement - Jackrabbit
> Affects Versions: 0.8
> Environment: Hudson build - 476
> Reporter: Alan Berg

> Assignee: Ian Boston

Reply all
Reply to author
Forward
0 new messages