tomcat 3.3.1 session bug
I have found the following bug: create a webapp called Test (note capitalization) in webapp Test, create index.jsp with the following line: session id = %=session.getId()% now try http://localhost:8080/test versus http://localhost:8080/Test refresh, the page you'll find that test generates a new session ID each time. where as Test has the correct behaviour and preserves the session ID. is this a known bug? is there anyone working on it? -Tony fyi: i'm running on win2k -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
possible JDBCRealm bug?
org.apache.tomcat.aaa.JDBCRealm opens a database connection and never closes the connection. Would not a more correct behaviour be to open/close the connection before/after verifying credentials? When the connection is kept open, the corresponding database is held up. For example, when using postgres, one cannot shutdown and restart the db server without first shutting down tomcat. thought? opinions? -Tony Chao -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
