tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Filip Hanik - Dev Lists <>
Subject Re: Servlet/session becoming null
Date Mon, 31 Jul 2006 19:11:22 GMT
if you are saying the tomcat session is dropped then, two reasons could be:

1. the session cookie is dropped
2. the session has expired (been idle longer than your timeout setting)

but your stack trace show TransactionSession, and it could be that your 
TransactionSession is holding a reference to the Tomcat session,
but the reference it is actually holding is a facade object, and the 
facade loses it connection to the delegate, hence the facade method.

Make sure you always get your reference to the session using the servlet 
API, and do NOT store a reference to it, as it is not the real session, 
just a facade object.


rache wrote:
> I have this error occuring when loading a jsp:
> 2006-07-28 17:33:01 StandardWrapperValve[debugjsp]: Servlet.service() for
> servlet debugjsp threw exception
> java.lang.NullPointerException
> 	at
> com.premier.ofa.core.TransactionSession.getAttribute(
> 	at
> com.premier.ofa.core.TransactionRequest.getConfigurationAttribute(
> 	at
> com.premier.SignOn.UserInqAuthTaskBean.isFeatureConfigured(
> 	at org.apache.jsp.jsp.security_jsp._jspService(
> 	at org.apache.jasper.runtime.HttpJspBase.service(
> 	at javax.servlet.http.HttpServlet.service(
> This happens on and off. In tracking the error, sometimes the session can be
> null. Why is this happening?
> Anyone familiar with this kind of exception?
> Thanks!

To start a new topic, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message