Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

session.invalidate()

1 view
Skip to first unread message

Eric Goldstein

unread,
May 22, 2001, 4:49:41 PM5/22/01
to

I am on WL 6.0 with sp1.
When I try to call session.invalidate() on the first hit to a servlet container
(a new session). I am then getting an IllegalStateException from the container.
Has anyone seen this behavior? Does anyone know a work around?
Here is the stacktrace:
java.lang.IllegalStateException: HttpSession is invalid
at weblogic.servlet.internal.session.SessionData.getAttribute(SessionDat
a.java:162)
at weblogic.servlet.internal.session.SessionData.getValue(SessionData.ja
va:134)
at weblogic.servlet.internal.ServletRequestImpl.getRemoteUser(ServletReq
uestImpl.java:805)
at weblogic.servlet.internal.HttpServer.logToFile(HttpServer.java:995)
at weblogic.servlet.internal.HttpServer.log(HttpServer.java:944)
at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImp
l.java:843)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:1627)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

James McGovern

unread,
Jul 5, 2001, 3:15:18 PM7/5/01
to
You will get an exception if the session has already been invalidated.

"Eric Goldstein" <er...@interworld.com> wrote in message
news:3b0ac2d5$1...@newsgroups.bea.com...

Billy Turchin

unread,
Jul 10, 2001, 4:38:28 PM7/10/01
to
This is not a problem because the session was previously invalidated. When you call invalidate() on a new session the call succeeds, but later WebLogic gets an error (see stack trace) when it makes a call to getAttribute(). Why does weblogic break when invalidate is called only on the first hit? Perhaps this exception should at least be caught silently in this case?
0 new messages