-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 AD,
On 7/7/2009 11:47 AM, AD wrote: > unfortunately still not working. One thing that i noticed, when i > clear my browser cookies, everything works fine again. One of the > things we do is use cookie persistence to send a user to the same > tomcat server (we need this for file uploads,etc). Can your firewall use /part/ of a cookie (or URL) to map the request to a server? If so, you can set the "route" of your <Connector> to annotate your session id with a unique moniker for the physical server: no need to do your own cookie management. > Is there anything > in the session cookie that would cause this issue? Doubtful. Are you doing anything strange like sticking DB connections into sessions or (intentionally) keeping connections open across requests? If you enable the debugging options on your <Resource>, do you see any error messages in your stdout log? I see from a later post that you are using Rails which has its own connection pool. You should look into the Rails DBCP setup and see if it has similar debugging options. Also, read my recent blog post on proper JDBC programming: http://blog.christopherschultz.net/?p=68 Hope that helps, - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkpX51wACgkQ9CaO5/Lv0PDcdACfcIlEbaG/KVpe1dFAII3pbnxS HoUAn0M0hEQsaJRLmYIeDX0/N3Ov6gjr =/Q79 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
