I wrote on "resin.conf = null when upgrading to Resin 4" (2009-06-02 06:48): > Sitting here trying to upgrade the dev environment to Resin 4.0 with > minimal changes to configuration and startup scripts. > On Windows I'm up and running ...
I apparently jumped the gun here. I am not up and running on Windows either. While picking up my resin.conf, Resin does not handle sessions but resets them on every request. Example "fine" log, first request: [20:56:44.359] SessionImpl[aaaQKDKMBgGTm9hnkvIgs,] new [20:56:44.359] SessionImpl[aaaQKDKMBgGTm9hnkvIgs,] create session ... Subsequent request: [20:57:27.250] Http[11] Cookie: JSESSIONID=aaaQKDKMBgGTm9hnkvIgs [20:57:27.750] SessionImpl[aaaQKDKMBgGTm9hnkvIgs,] reset [20:57:27.750] SessionImpl[aaaQKDKMBgGTm9hnkvIgs,] reset [20:57:27.750] SessionImpl[aaaQKDKMBgGTm9hnkvIgs,] new [20:57:27.750] SessionImpl[aaaQKDKMBgGTm9hnkvIgs,] create session Tried to find a configuration fault by debugging, but I end up really confused. When com.caucho.server.session.SessionImpl.save() is entered, I have a couple of values in the session, but when stepping into the isValid() the _values Map is suddenly empty??? Here is my session config: <persistent-store type="file"> <init> <path>c:\temp\resin-sessions</path> <always-save>true</always-save> </init> </persistent-store> + <session-config> <use-persistent-store /> <session-max>4096</session-max> <session-timeout>30</session-timeout> </session-config> -- </Mattias> _______________________________________________ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
