• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Unknown error: "close session with active objects"

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Howdy,

We're running into a problem where something is breaking in our sessions. The exact situation is that our server is running with two agent-nodes on the same machine; one node-agent behaves as expected, and the other constantly produces the stack trace shown below.

The question is: has anyone encountered this type of problem before? There are remarkable few google hits for "close session with active objects", so I'm guessing this is a rare pheomenon.

Does this look like an SSL problem? A Sun-specific bug? A configuration problem with the high-availability database that stores these sessions between the two instances?



We are running (on some fancy-pants Sun hardware): Sun Java System Application Server Enterprise Edition 8.1_02 (build b06-fcs). As mentioned, there are two instances on the same machine. There is an http-load balancer in front of these two instances.

Any help or further clues -- even just "me-too" posts -- would be helpful. Thanks!
 
Paul Forest
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
*bump*

Any bites on this?
 
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Did you ever manage to resolve this issue?

I have a similar issue on Solaris 10 and Sun App Server 8.1.


stack trace :

java.security.ProviderException: Internal error: close session with active objects
sun.security.pkcs11.SessionManager.closeSession(SessionManager.java:197)
sun.security.pkcs11.SessionManager.access$000(SessionManager.java:48)
sun.security.pkcs11.SessionManager$Pool.release(SessionManager.java:253)
sun.security.pkcs11.SessionManager.releaseSession(SessionManager.java:155)
sun.security.pkcs11.Token.releaseSession(Token.java:245)
sun.security.pkcs11.P11SecureRandom.engineNextBytes(P11SecureRandom.java:98)
java.security.SecureRandom.nextBytes(SecureRandom.java:413)
java.security.SecureRandom.next(SecureRandom.java:435)
java.util.Random.nextInt(Random.java:188)
com.sun.enterprise.util.uuid.UuidUtil.getNextInt(UuidUtil.java:142)
com.sun.enterprise.util.uuid.UuidUtil.getNextRandomString(UuidUtil.java:146)
com.sun.enterprise.util.uuid.UuidUtil.generateUuid(UuidUtil.java:50)
com.sun.enterprise.util.uuid.UuidGeneratorImpl.generateUuid(UuidGeneratorImpl.java:25)
org.apache.catalina.session.ManagerBase.generateSessionId(ManagerBase.java:993)
org.apache.catalina.session.ManagerBase.createSession(ManagerBase.java:796)
org.apache.catalina.session.StandardManager.createSession(StandardManager.java:292)
org.apache.coyote.tomcat5.CoyoteRequest.doGetSession(CoyoteRequest.java:2365)
org.apache.coyote.tomcat5.CoyoteRequest.getSession(CoyoteRequest.java:2202)
org.apache.coyote.tomcat5.CoyoteRequestFacade.getSession(CoyoteRequestFacade.java:838)
javax.servlet.http.HttpServletRequestWrapper.getSession(HttpServletRequestWrapper.java:265)
com.localmatters.mvc.web.filter.AptasServletRequestWrapper.getSession(AptasServletRequestWrapper.java:184)
com.localmatters.mvc.web.filter.AptasServletRequestWrapper.getSession(AptasServletRequestWrapper.java:170)
com.aptas.etosha.web.handler.ExceptionResolver.getModelAndView(ExceptionResolver.java:76)
org.springframework.web.servlet.handler.SimpleMappingExceptionResolver.resolveException(SimpleMappingExceptionResolver.java:174)
com.aptas.etosha.web.handler.ExceptionResolver.resolveException(ExceptionResolver.java:96)
org.springframework.web.servlet.DispatcherServlet.processHandlerException(DispatcherServlet.java:915)
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:739)
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:663)
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:394)
org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:348)
javax.servlet.http.HttpServlet.service(HttpServlet.java:747)
javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
com.aptas.etosha.filters.InterceptorFilter.doFilter(InterceptorFilter.java:56)
org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:137)
com.localmatters.mvc.web.filter.AbstractSpiderFilter.doFilter(AbstractSpiderFilter.java:94)
org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:137)
com.localmatters.mvc.web.filter.EtoshaFilter.doFilter(EtoshaFilter.java:107)
 
reply
    Bookmark Topic Watch Topic
  • New Topic