tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cmanola...@yahoo.com
Subject Re: cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/modules/session SimpleSessionStore.java
Date Mon, 26 Mar 2001 20:08:43 GMT
>   Temporary(?) fix to stop crashes when creating a new Session in
> embedded use of Jasper (i.e. as standalone JspServlet ).  Problem may
> occur in other situations as well, I'm not sure.
>   
>   Problem:  When
> SimpleSessionStore.SimpleSessionManager.getNewSession() is called (as a
> result of a call to request.getSession(), the session ID of the new
> session has not been set.  Since it is implemented as a MessageBytes

Hi Mel, 

I looked at that and I couldn't reproduce it - are you sure you have the 
right configuration ( i.e. SessionIdGenerator included in server.xml ) ?

getNewSession is calling setState( STATE_NEW ), that calls the
sessionState callback that allows modules to initialize the new session
object - and SessionIdGenerator is setting the id ( using whatever
random). 

I can't understand what's wrong - my only guess is that SessionIdGenerator
is not included.

I didn't had too much time this weekend ( to restart the nightly tests ),
but I hope to resolve those issues soon.

Costin



> object, the .toString() method to get a string representation of the
> session id returns null.  When getNewSession() tries to use this value
> as a key into the sessions hashtable, a NullPointerException is thrown.






Mime
View raw message