michael brosnahan

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)

I have also run this jsp through tomcat and got the same results.
It looks to me that the web container is running the jsp page through the same instance but one at a time. The numbers never repeat which show that it is thread safe (ie only one thread in _jspService at a time). The processing take quite a while indicating it is single threaded.
I have done a similar experiment on a servlet and got slightly different results. aTomcat created two instances of the servlet and ran all the requests through these 2 instances.

This information is from the web.xml ddt at: http://java.sun.com/j2ee/dtds/web-app_2_2.dtd
"The transport-guarantee element specifies that the communication between client and server should be NONE, INTEGRAL, or CONFIDENTIAL.
NONE means that the application does not require any transport guarantees.
INTEGRAL means that the application requires that the data sent between the client and server be sent in such a way that it can't be changed in transit.
CONFIDENTIAL means that the application requires that the data be transmitted in a fashion that prevents other entities from observing the contents of the transmission.
In most cases, the presence of the INTEGRAL or CONFIDENTIAL flag will indicate that the use of SSL is required."

HttpServletRequest parameters can not be set. They can only be got.
The only thing that can be set on a request is attributes

Filters are not covered in the exam

The setStatus method is used to set the return status code when there is no error (for example, for the status codes SC_OK or SC_MOVED_TEMPORARILY).
sendError sends an error response to the client.
If you have declared an error-page for the particular error code in the web.xml file that error page will be sent to the client.

Thanks,
I found out my issue was that I had the wrong dtd definition in the web.xml file. The one I have was pointing to servley 2.2, once I change this it all worked fine.

I am building a example web app in tomcat as part of my study. I have tried to use the listener tag in the web.xml file but tomcat throws an expection when it tries to digest the web.xml as it can't parse the listener tag. The exception lists the the dtd entry for the web-app tag and the listener tag is not is even in it.
Could this be caused by an old version of Tomcat or an old version of servlet.jar?

Hi all,
I'm looking at sitting my certification exam in about 6 weeks. I'm currently studing objective by objective.
What I'm looking for is mock exam questions that have been grouped by objective. I have found some partial examples of this but not a full list. Does anyone know if such a resource exists? :roll: