DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16316>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16316 DataSourceRealm can not find JNDI name in context ------- Additional Comments From [EMAIL PROTECTED] 2003-06-26 20:34 ------- I too believe this should be re-opened and fixed. Our manifestation of the defect is a little different. Again, our "webapps/appname.xml" file defines both the JDBCRealm and our application datasource. Both authentication and application database access work initially - UNTIL things go inactive and the MySQL 8hr timeout occurs. The fix for this is supposed to be to add "?autoReconnect=true" to the end of the JDBC URL - so we added this. However this does not fix the problem, the timeouts during authentication still occur. Moving the entire context (with both datasource and JDBCRealm within) to server.xml appears to fix the timeouts. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
