Re: JDBCRealm changes from Tomcat 5.0.x to 5.5.x
I had similar problems, and was forced to revert back to Tomcat 5.0.x. Are you using HTTP or Form-based authentication to get the user credentials? On Tue, 2005-03-08 at 11:57 -0700, Richard Mixon (qwest) wrote: Has anything changed with the way that JDBCReal handles connection timeouts in Tomcat 5.5.7? We upgraded from Tomcat 5.0.19 to Tomcat 5.5.7 in production and are now getting JDBC connection errors when the site has not been accessed for a while. This is happening when a user tries to login - we use a JDBCRealm to authenticate the user. We had this problem a while back but fixed it by adding the autoReconnect parm, but now with Tomcat 5.5. we are having the problem again. We are using MySQL 4.1.7 and version 3.1.7 of the MySQL JDBC connector. Here is the realm specification: Realm className=org.apache.catalina.realm.JDBCRealm debug=99 driverName=com.mysql.jdbc.Driver connectionURL=jdbc:mysql://dbserver1:3306/webapp1?autoReconnect=tru eamp;autoCommit=true connectionName=user1 connectionPassword=password1 userTable=PoPerson userNameCol=userid userCredCol=password userRoleTable=PoPersonRole roleNameCol=roleName / Resource name=jdbc/webapp1 type=javax.sql.DataSource auth=Container maxActive=100 maxIdle=10 maxWait=1 defaultAutoCommit=true username=user1 password=password1 driverClassName=com.mysql.jdbc.Driver url=jdbc:mysql://dbserver1:3306/ltojsw?autoRecon nect=trueamp;autoCommit=true removeAbandoned=true removeAbandonedTimeout=60 logAbandoned=true / I also included the corresponding datasource defined for actual application access. The actual exception is below. Would using the DataSourceReal provide any help here? I was thinking that since it uses DBCP pooling maybe timeout recovery might be more robust. I am trying to duplicate the problem in development now, before trying the DataSourceRealm. Thank you all for any suggestions or solutions. - Richard Here is the exception: 16:50:00,269 ERROR [TP-Processor6] [/stars]:541 - Exception retrieving password for wazinger com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception: ** BEGIN NESTED EXCEPTION ** java.net.SocketException MESSAGE: Broken pipe STACKTRACE: java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123) at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:2616) at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:2547) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1512) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1622) at com.mysql.jdbc.Connection.execSQL(Connection.java:2376) at com.mysql.jdbc.Connection.execSQL(Connection.java:2297) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java: 1860) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:170 5) at org.apache.catalina.realm.JDBCRealm.getPassword(JDBCRealm.java:526) at org.apache.catalina.realm.JDBCRealm.authenticate(JDBCRealm.java:399) at org.apache.catalina.realm.JDBCRealm.authenticate(JDBCRealm.java:347) at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAut henticator.java:256) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authenticator Base.java:391) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :126) at org.apache.catalina.cluster.tcp.ReplicationValve.invoke(ReplicationValve .java:130) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java :105) at org.apache.catalina.valves.FastCommonAccessLogValve.invoke(FastCommonAcc essLogValve.java:481) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:1 48) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:306) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:385) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:745) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java: 675) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:868) at
RE: JDBCRealm changes from Tomcat 5.0.x to 5.5.x
We are using form-based authentication. We changed to the DataSourceRealm last weekend and it appears (so far) to have solved the problem (again with TC 5.5.7 plus session replication patch). - Richard Darren Govoni wrote: I had similar problems, and was forced to revert back to Tomcat 5.0.x. Are you using HTTP or Form-based authentication to get the user credentials? On Tue, 2005-03-08 at 11:57 -0700, Richard Mixon (qwest) wrote: Has anything changed with the way that JDBCReal handles connection timeouts in Tomcat 5.5.7? We upgraded from Tomcat 5.0.19 to Tomcat 5.5.7 in production and are now getting JDBC connection errors when the site has not been accessed for a while. This is happening when a user tries to login - we use a JDBCRealm to authenticate the user. We had this problem a while back but fixed it by adding the autoReconnect parm, but now with Tomcat 5.5. we are having the problem again. We are using MySQL 4.1.7 and version 3.1.7 of the MySQL JDBC connector. Here is the realm specification: Realm className=org.apache.catalina.realm.JDBCRealm debug=99 driverName=com.mysql.jdbc.Driver connectionURL=jdbc:mysql://dbserver1:3306/webapp1?autoReconnect=tru eamp;autoCommit=true connectionName=user1 connectionPassword=password1 userTable=PoPerson userNameCol=userid userCredCol=password userRoleTable=PoPersonRole roleNameCol=roleName / Resource name=jdbc/webapp1 type=javax.sql.DataSource auth=Container maxActive=100 maxIdle=10 maxWait=1 defaultAutoCommit=true username=user1 password=password1 driverClassName=com.mysql.jdbc.Driver url=jdbc:mysql://dbserver1:3306/ltojsw?autoRecon nect=trueamp;autoCommit=true removeAbandoned=true removeAbandonedTimeout=60 logAbandoned=true / I also included the corresponding datasource defined for actual application access. The actual exception is below. Would using the DataSourceReal provide any help here? I was thinking that since it uses DBCP pooling maybe timeout recovery might be more robust. I am trying to duplicate the problem in development now, before trying the DataSourceRealm. Thank you all for any suggestions or solutions. - Richard Here is the exception: 16:50:00,269 ERROR [TP-Processor6] [/stars]:541 - Exception retrieving password for wazinger com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception: ** BEGIN NESTED EXCEPTION ** java.net.SocketException MESSAGE: Broken pipe STACKTRACE: java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123) at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:2616) at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:2547) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1512) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1622) at com.mysql.jdbc.Connection.execSQL(Connection.java:2376) at com.mysql.jdbc.Connection.execSQL(Connection.java:2297) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java: 1860) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:170 5) at org.apache.catalina.realm.JDBCRealm.getPassword(JDBCRealm.java:526) at org.apache.catalina.realm.JDBCRealm.authenticate(JDBCRealm.java:399) at org.apache.catalina.realm.JDBCRealm.authenticate(JDBCRealm.java:347) at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAut henticator.java:256) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authenticator Base.java:391) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java 126) at org.apache.catalina.cluster.tcp.ReplicationValve.invoke(ReplicationValve .java:130) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java 105) at org.apache.catalina.valves.FastCommonAccessLogValve.invoke(FastCommonAcc essLogValve.java:481) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:1 48) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:306) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:385) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:745) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java: 675) at
RE: JDBCRealm changes from Tomcat 5.0.x to 5.5.x
Well, I'm running that configuration in 5.5.7, yes. Holds water so far. But this has been done by directly editing server.xml - so it's not really a self-contained webapp configuration. Best regards, -- David --On Thursday, March 10, 2005 9:48 AM -0500 Phillip Qin [EMAIL PROTECTED] wrote: Very useful info. Thx. Have you actually tested your configure in tc5.5.7/.8, i.e. Tomcat Manager app deploy/redeploy etc.? -Original Message- From: David Tonhofer, m-plify S.A. [mailto:[EMAIL PROTECTED] Sent: March 10, 2005 5:55 AM To: Tomcat Users List Subject: Re: JDBCRealm changes from Tomcat 5.0.x to 5.5.x Juste pour info: I have written up my DataSourceRealm with DBCP that I got working before 02:00 this night (eww) into the DBCP Twiki. Not the best place, but hey, might be useful: http://wiki.apache.org/jakarta-commons/DBCP Enjoy, -- David --On Wednesday, March 09, 2005 8:40 PM -0800 alexander dosher [EMAIL PROTECTED] wrote: Hassan Schroeder makes my day: How about something like: (the correct answer) YES, thank you. i had a resourceName instead of a dataSourceName in my DataSourceRealm, left over from trying to use a UserDatabaseRealm, which i didn't really understand and isn't even in the docs anymore anyway. duh. *and* this method *is* reopening connections, which JDBCRealm didn't. yay! dream. code. no, thank you. had an awk dream once. i don't recommend it. ;-) --alex. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JDBCRealm changes from Tomcat 5.0.x to 5.5.x
Juste pour info: I have written up my DataSourceRealm with DBCP that I got working before 02:00 this night (eww) into the DBCP Twiki. Not the best place, but hey, might be useful: http://wiki.apache.org/jakarta-commons/DBCP Enjoy, -- David --On Wednesday, March 09, 2005 8:40 PM -0800 alexander dosher [EMAIL PROTECTED] wrote: Hassan Schroeder makes my day: How about something like: (the correct answer) YES, thank you. i had a resourceName instead of a dataSourceName in my DataSourceRealm, left over from trying to use a UserDatabaseRealm, which i didn't really understand and isn't even in the docs anymore anyway. duh. *and* this method *is* reopening connections, which JDBCRealm didn't. yay! dream. code. no, thank you. had an awk dream once. i don't recommend it. ;-) --alex. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JDBCRealm changes from Tomcat 5.0.x to 5.5.x
On Wed, 09 Mar 2005 17:39:21 -0800, alexander dosher [EMAIL PROTECTED] wrote: and an Engine Realm className=org.apache.catalina.realm.DataSourceRealm name=UserDatabase and i get java.lang.NullPointerException at javax.naming.NameImpl.init at javax.naming.CompositeName.init at org.apache.naming.NamingContext.lookup (etc.) so please accept my application to the Frustration Club. :( You get a membership to the RTFM club instead ;) http://jakarta.apache.org/tomcat/tomcat-5.5-doc/realm-howto.html#DataSourceRealm The JDBC realm in 5.5.8 obviously still has the bug related to connection handling, as I only fixed it two days ago. -- x Rémy Maucherat Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JDBCRealm changes from Tomcat 5.0.x to 5.5.x
Very useful info. Thx. Have you actually tested your configure in tc5.5.7/.8, i.e. Tomcat Manager app deploy/redeploy etc.? -Original Message- From: David Tonhofer, m-plify S.A. [mailto:[EMAIL PROTECTED] Sent: March 10, 2005 5:55 AM To: Tomcat Users List Subject: Re: JDBCRealm changes from Tomcat 5.0.x to 5.5.x Juste pour info: I have written up my DataSourceRealm with DBCP that I got working before 02:00 this night (eww) into the DBCP Twiki. Not the best place, but hey, might be useful: http://wiki.apache.org/jakarta-commons/DBCP Enjoy, -- David --On Wednesday, March 09, 2005 8:40 PM -0800 alexander dosher [EMAIL PROTECTED] wrote: Hassan Schroeder makes my day: How about something like: (the correct answer) YES, thank you. i had a resourceName instead of a dataSourceName in my DataSourceRealm, left over from trying to use a UserDatabaseRealm, which i didn't really understand and isn't even in the docs anymore anyway. duh. *and* this method *is* reopening connections, which JDBCRealm didn't. yay! dream. code. no, thank you. had an awk dream once. i don't recommend it. ;-) --alex. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] !DSPAM:4230275a152948713912020!
RE: JDBCRealm changes from Tomcat 5.0.x to 5.5.x
Could any one who has tested it post his result? I am really frustrated by the sometime buggy 5.5 releases and I had to revert to 5.0.28. -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED] Sent: March 8, 2005 6:23 PM To: Tomcat Users List Subject: Re: JDBCRealm changes from Tomcat 5.0.x to 5.5.x On Tue, 08 Mar 2005 15:16:41 -0800, Hassan Schroeder [EMAIL PROTECTED] wrote: Richard Mixon (qwest) wrote: We upgraded from Tomcat 5.0.19 to Tomcat 5.5.7 in production and are now getting JDBC connection errors when the site has not been accessed for a while. This is happening when a user tries to login - we use a JDBCRealm to authenticate the user. Would using the DataSourceReal provide any help here? I'm using a DataSourceRealm with 5.5.7 and not seeing any problems reconnecting at any time (MySQL 4.1.7 + Connector/J 3.1.6)... Be careful about this bug with the DataSourceRealm (fixed in 5.5.8): http://issues.apache.org/bugzilla/show_bug.cgi?id=33357 Similarly, I would appreciate testing of the fix. I agree there's absolutely no reason to use the regular JDBC realm, which can be a bottleneck in some cases. -- x Rémy Maucherat Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] !DSPAM:422e33ec287371584411517!
Re: JDBCRealm changes from Tomcat 5.0.x to 5.5.x
On Wed, 9 Mar 2005 10:40:37 -0500, Phillip Qin [EMAIL PROTECTED] wrote: Could any one who has tested it post his result? I am really frustrated by the sometime buggy 5.5 releases and I had to revert to 5.0.28. You can also use the realms form 5.5.4, as they don't have problems. The regressions were introduced when adding digest authentication support to the database realms. -- x Rémy Maucherat Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JDBCRealm changes from Tomcat 5.0.x to 5.5.x
Phillip Qin [EMAIL PROTECTED]: Could any one who has tested it post his result? I am really frustrated by the sometime buggy 5.5 releases and I had to revert to 5.0.28. here's a summation of my experiences interpretations of answers from the list, so far: JDBCRealm (5.5.4): worked i think, but no longer available on tomcat website that i can find JDBCRealm (5.5.7, 5.5.8a): doesn't reopen dropped connections DataSourceRealm (5.5.4): doesn't support digest authentication DataSourceRealm (5.5.7): doesn't work or is unconfigurable by me - i've got a Server GlobalNamingResources Resource type=javax.sql.DataSource name=UserDatabase and an Engine Realm className=org.apache.catalina.realm.DataSourceRealm name=UserDatabase and i get java.lang.NullPointerException at javax.naming.NameImpl.init at javax.naming.CompositeName.init at org.apache.naming.NamingContext.lookup (etc.) so please accept my application to the Frustration Club. :( --alex. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JDBCRealm changes from Tomcat 5.0.x to 5.5.x
alexander dosher wrote: DataSourceRealm (5.5.7): doesn't work or is unconfigurable by me - i've got a Server GlobalNamingResources Resource type=javax.sql.DataSource name=UserDatabase and an Engine Realm className=org.apache.catalina.realm.DataSourceRealm name=UserDatabase snip/ How about something like: GlobalNamingResources Resource name=jdbc/authorization auth=Container type=javax.sql.DataSource username=ren password=stimpy driverClassName=com.mysql.jdbc.Driver url=jdbc:mysql://localhost:3306/authority?autoReconnect=true/ /GlobalNamingResources :: and :: Realm className=org.apache.catalina.realm.DataSourceRealm dataSourceName=jdbc/authorization userTable=users userNameCol=user_name userCredCol=user_pass userRoleTable=user_roles roleNameCol=role_name/ :: which -- season to taste -- works for me :-) FWIW! -- Hassan Schroeder - [EMAIL PROTECTED] Webtuitive Design === (+1) 408-938-0567 === http://webtuitive.com dream. code. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JDBCRealm changes from Tomcat 5.0.x to 5.5.x
Hassan Schroeder makes my day: How about something like: (the correct answer) YES, thank you. i had a resourceName instead of a dataSourceName in my DataSourceRealm, left over from trying to use a UserDatabaseRealm, which i didn't really understand and isn't even in the docs anymore anyway. duh. *and* this method *is* reopening connections, which JDBCRealm didn't. yay! dream. code. no, thank you. had an awk dream once. i don't recommend it. ;-) --alex. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
re: JDBCRealm changes from Tomcat 5.0.x to 5.5.x
i'm getting the same problem, w/MySQL 4.1.8 3.1.6 connector (except my error is Software caused connection abort rather than broken pipe - but same underlying cause, MySQL timing out the connection). autoReconnect doesn't work for me either. sounds like perhaps i should bail on 5.5.* go to 5.0 for a while? We upgraded from Tomcat 5.0.19 to Tomcat 5.5.7 in production and are now getting JDBC connection errors when the site has not been accessed for a while. This is happening when a user tries to login - we use a JDBCRealm to authenticate the user. We had this problem a while back but fixed it by adding the autoReconnect parm, but now with Tomcat 5.5. we are having the problem again. We are using MySQL 4.1.7 and version 3.1.7 of the MySQL JDBC connector. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JDBCRealm changes from Tomcat 5.0.x to 5.5.x
On Tue, 08 Mar 2005 14:28:12 -0800, alexander dosher [EMAIL PROTECTED] wrote: i'm getting the same problem, w/MySQL 4.1.8 3.1.6 connector (except my error is Software caused connection abort rather than broken pipe - but same underlying cause, MySQL timing out the connection). autoReconnect doesn't work for me either. sounds like perhaps i should bail on 5.5.* go to 5.0 for a while? I'd be extremely glad if you could test this possibly fixed realm. Replace the existing class in server/lib/catalina-optional.jar. -- x Rémy Maucherat Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JDBCRealm changes from Tomcat 5.0.x to 5.5.x
Richard Mixon (qwest) wrote: We upgraded from Tomcat 5.0.19 to Tomcat 5.5.7 in production and are now getting JDBC connection errors when the site has not been accessed for a while. This is happening when a user tries to login - we use a JDBCRealm to authenticate the user. Would using the DataSourceReal provide any help here? I'm using a DataSourceRealm with 5.5.7 and not seeing any problems reconnecting at any time (MySQL 4.1.7 + Connector/J 3.1.6)... FWIW, -- Hassan Schroeder - [EMAIL PROTECTED] Webtuitive Design === (+1) 408-938-0567 === http://webtuitive.com dream. code. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JDBCRealm changes from Tomcat 5.0.x to 5.5.x
On Tue, 08 Mar 2005 15:16:41 -0800, Hassan Schroeder [EMAIL PROTECTED] wrote: Richard Mixon (qwest) wrote: We upgraded from Tomcat 5.0.19 to Tomcat 5.5.7 in production and are now getting JDBC connection errors when the site has not been accessed for a while. This is happening when a user tries to login - we use a JDBCRealm to authenticate the user. Would using the DataSourceReal provide any help here? I'm using a DataSourceRealm with 5.5.7 and not seeing any problems reconnecting at any time (MySQL 4.1.7 + Connector/J 3.1.6)... Be careful about this bug with the DataSourceRealm (fixed in 5.5.8): http://issues.apache.org/bugzilla/show_bug.cgi?id=33357 Similarly, I would appreciate testing of the fix. I agree there's absolutely no reason to use the regular JDBC realm, which can be a bottleneck in some cases. -- x Rémy Maucherat Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JDBCRealm changes from Tomcat 5.0.x to 5.5.x
Hassan, Could it be that you do not experience the long periods of inactivity on weekends that we do? This only happens on the weekend when we have low activity - sometimes one of the Tomcat instances (they are clustered) will not see a login request for about a half-day. During the week, the longest inactive period is usually about six hours. - Richard -Original Message- From: Hassan Schroeder [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 08, 2005 4:17 PM To: Tomcat Users List Subject: Re: JDBCRealm changes from Tomcat 5.0.x to 5.5.x Richard Mixon (qwest) wrote: We upgraded from Tomcat 5.0.19 to Tomcat 5.5.7 in production and are now getting JDBC connection errors when the site has not been accessed for a while. This is happening when a user tries to login - we use a JDBCRealm to authenticate the user. Would using the DataSourceReal provide any help here? I'm using a DataSourceRealm with 5.5.7 and not seeing any problems reconnecting at any time (MySQL 4.1.7 + Connector/J 3.1.6)... FWIW, -- Hassan Schroeder - [EMAIL PROTECTED] Webtuitive Design === (+1) 408-938-0567 === http://webtuitive.com dream. code. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JDBCRealm changes from Tomcat 5.0.x to 5.5.x
Remy, Thanks - but where do I get the new class file? - Richard -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 08, 2005 4:01 PM To: Tomcat Users List Subject: Re: JDBCRealm changes from Tomcat 5.0.x to 5.5.x On Tue, 08 Mar 2005 14:28:12 -0800, alexander dosher [EMAIL PROTECTED] wrote: i'm getting the same problem, w/MySQL 4.1.8 3.1.6 connector (except my error is Software caused connection abort rather than broken pipe - but same underlying cause, MySQL timing out the connection). autoReconnect doesn't work for me either. sounds like perhaps i should bail on 5.5.* go to 5.0 for a while? I'd be extremely glad if you could test this possibly fixed realm. Replace the existing class in server/lib/catalina-optional.jar. -- x Rémy Maucherat Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JDBCRealm changes from Tomcat 5.0.x to 5.5.x
On Tue, 8 Mar 2005 16:28:22 -0700, Richard Mixon (qwest) [EMAIL PROTECTED] wrote: Remy, Thanks - but where do I get the new class file? The Apache mail server, which, BTW, must be the worst mail server in existence, chooses to let through all the viruses and spammers of the world, but is refusing my perfectly legitimate attachement. So sorry, you have to either build it from CVS (which is easy) or get it from a nightly build. I'd like to add that the DataSource realm works differently from the JDBC realm. As a result, it would reconnect transparently, and the problem you have won't occur. If you decide to try the data source realm, I recommend using the version from 5.5.8, unless you expect a really low amount of authentications (it will take a little time for the connection pool to reclaim the resources which are not properly closed by the realm). -- x Rémy Maucherat Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JDBCRealm changes from Tomcat 5.0.x to 5.5.x
Richard Mixon (qwest) wrote: Hassan, Could it be that you do not experience the long periods of inactivity on weekends that we do? No, I'm using this for both my own dev workbench and an intranet server at the moment, and at the least they're idled out overnight. So there's not enough authentication traffic to really show up the 33357 bug, but I *certainly* exceed the connection timeout period. -- Hassan Schroeder - [EMAIL PROTECTED] Webtuitive Design === (+1) 408-938-0567 === http://webtuitive.com dream. code. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JDBCRealm changes from Tomcat 5.0.x to 5.5.x
I'd be extremely glad if you could test this possibly fixed realm. Replace the existing class in server/lib/catalina-optional.jar. ... you have to either build it from CVS (which is easy) or get it from a nightly build. M. Maucherat, thank you for the suggestion, but i'm not sufficiently (i.e. at all) CVS-savvy to get the nightly build - and there's either no web access or cvs.apache.org/builds/jakarta-timcat-5/nightly/ is in fact empty. i tried upgrading the whole server to 5.5.8-alpha in case your changes were already there, but i still get the same error. if you'd care to send me the updated catalina-optional.jar directly i'd be happy to try to test it again, and will also look into the DataSource realm as you suggest. thanks, alex. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
