Thanks for the quick answer.
I looked in the catalina log and found a serialize exception corrected the error and now it works fine!
Best Regards Christian Bach
Henning P. Schmiedehausen wrote:
Christian Bach <[EMAIL PROTECTED]> writes:
The session storage should be completely transparent from the application view. The only thing that _could_ bite you are non-Serializable objects. Do you get any exceptions in the catalina.out log?
Regards Henning
I was wondering if anyone have had problems storing Turbine sessions in a database?
Iv modified the context manager for the app to store the sessions in the database, but it seems to fail.
Perhaps this is a Tomcat issue rather then Turbine?
I using Tomcat 5.0.30, Turbine 2.3.1 and Torque 3.1.1
Best regards
Christian Bach
<http://apache.dataphone.se/jakarta/tomcat-5/v5.0.30>
<http://www.polyester.se>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
------------------------------------------- *POLYESTER** Wittstocksgatan 2 NB 115 24 STOCKHOLM Tel: 08 - 660 73 50 Mobil: 070 - 443 91 90 E-post: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> http://www.polyester.se
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
