Girish Juneja wrote:
>
> Resending it for lack of response the last time around:
>
> I have an interesting problem with session invalidation. I have a servlet
> that if invoked with a
> certain parameters, needs to dump the session it has, and create a new one.
>
> For this purpose I invalidate the session using
> request.getSession(true).invalidate() method when
> the servlet notices those certain parameters. Soon after that in code, I
> check for
> request.isRequestedSessionIdValid() and it returns true!! After that I do
> another
> request.getSession(true) and the sessionId is still the same suggesting
> that getSession
> did not get me a new session.
>
> Interestingly, on the next call to this servlet, the session id (from
> getSession(true).getId()) is new.
> Implying that somehow, during the same servlet instance, the session id
> invalidation did
> not take effect but on a new invocation it did.
>
> Can someone explain what is going on? Is there something I am doing wrong?
> I am using BEA
> weblogic webserver which has a servlet environment built in.
As far as I can tell you're not doing anything wrong. It's more likely
a bug in the WebLogic server. I suggest you snd the question to their
support group.
--
Hans Bergsten [EMAIL PROTECTED]
Gefion Software http://www.gefionsoftware.com
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
