session error when invalidating

[TSkill]

Was wondering if anyone else has seen this or knows whats going on. I
recently migrated from WAS 2 to 3.0.2 and now Im getting an error everytime
a user logs off the site. when they chose a logoff option from the side menu
bar, i run a simple servlet called "LogoffHandler" that just redirects the
user back to the login page and invalidates the users session. everything
seems to execute fine, the user gets redirected to login page, but after the
servlet executes I always get this error.

Thanks for the help.

Tom
tsk...@securitylink.com

Here's the code in the doGet that causes the error after it executes:

HttpSession session = req.getSession ( true );
res.sendRedirect ( loginPage );

if ( session != null )
{
session.invalidate();
}

Here's the first part of the stack trace:

766.332 189b5a WebGroup A [Servlet.LOG]:."Original Error:
":.com.ibm.servlet.engine.webapp.WebAppErrorReport: [LogoffHandler] reported
an error
at
com.ibm.servlet.engine.webapp.WebAppDispatcherResponse.sendError(WebAppDispa
tcherContext.java:240)
at
com.ibm.servlet.engine.webapp.WebAppDispatcherResponse.sendError(WebAppDispa
tcherContext.java:219)
at
com.ibm.servlet.engine.webapp.WebAppDispatcherResponse.sendRedirect(WebAppDi
spatcherContext.java:203)
at
com.securitylink.infoshare.servlets.LogoffHandler.doGet(LogoffHandler.java:4
2)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:534)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:639)
at
com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager
.java:557)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycl
eServlet.java:160)
at
com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServle
t.java:287)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycle
Servlet.java:105)
at
com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:34
9)
at
com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletMan
ager.java:705)
at
com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManag
er.java:631)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(W
ebApp.java:1129)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebApp.java:1
001)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebApp.java:96
0)
at
com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebGroup.java:
681)
at
com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedIn
vocation.java:67)
at
com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequ
estProcessor.java:139)