• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 678
  • Last Modified:

WSAD session timeout

Hi,
 I deployed my application using WSAD5.1.0.
 Its a web based application using STRUTS framework. If my browser is idle for sometime
 and if I test my application again, I'm getting NullPointerException.
 I did set my <session-timeout> as 0 in my web.xml. Even though, I'm getting nullpointer
 in my application.
 So to avoid, I have to relogin in my application. My application does not
 check for any timeout. Is there anything else I need to set in my config ? (I checked WSAD admin
 console for timeout setting but I didn't find anything)
 Any idea ?
 
 
 [9/2/04 13:51:57:542 CDT] 31d59858 WebGroup      E SRVE0026E: [Servlet Error]-[]: java.lang.NullPointerException
       at com.x.y.x.action.MyAction.execute(MyAction.java:80)
       at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
       at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
       at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
       at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
       at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
       at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
       at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
       at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
       at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
       at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
       at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
       at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:948)
       at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:530)
       at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:176)
       at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:79)
       at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:201)
       at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
       at com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:114)
       at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:186)
       at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
       at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
       at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:610)
       at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:431)
       at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)

Thanks.
0
rameshaa
Asked:
rameshaa
1 Solution
 
mmichrinCommented:
Give this a shot...

In the WAS admin console, navigate to Servers->Application Servers->server1->web container->session management and modify the 'session timeout' property (disable the timeout, or change the amount of time for the timeout.

Mark
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now