-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jerry,
On 4/15/2009 11:58 PM, jerrySheen wrote:
> So u mean to say, that if I were to prolong the JSESSIONID cookie's expiry
> time, the server would take care of repopulating the session state(stored in
> the db) even after a browser restart?
>
> We
So u mean to say, that if I were to prolong the JSESSIONID cookie's expiry
time, the server would take care of repopulating the session state(stored in
the db) even after a browser restart?
Well, this seems like a much simpler solution,ill give it a try, hope it
works.
Thanks,
JS
--
View this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jerry,
On 4/13/2009 11:15 PM, jerrySheen wrote:
> As we are dealing with sessions that are no [longer accessible], this action
> would have no effect on any live sessions thus no inconsistencies.
>
>> if YES, please furnish some sample code or at lea
can someone please reply to the above post.:-((
--
View this message in context:
http://www.nabble.com/retrieve-session-data-stored-in-db-using-JDBCStore.-tp23020556p23052044.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
Why?
The risk is that you will introduce inconsistencies into live sessions.
Surely modifying the session using the API provided by the Servlet spec
is a) safer and b) easier.
As we are dealing with sessions that are no more accessable, this action
would have no effect on any live sessions thus no
jerrySheen wrote:
> Hi,
> I have been successful in saving the sessions to my mysql db, using the
> given code in my server configuration file.
>
>
> connectionURL="jdbc:mysql://X/xx?user=z&password=zz"
> driverName="com.mysql.jdbc.Driver"
> sessio