Re: 7.0.4 problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark, On 11/13/2010 7:26 AM, Mark Thomas wrote: I think you have hit this: https://issues.apache.org/bugzilla/show_bug.cgi?id=50159 Technically, 7.0.4 is sticking to the letter of the J2EE spec but it isn't what applications expect. 7.0.5 will revert to the previous behaviour but with an configurable option for those folks who want their resource factories to behave differently. I've just read that bug description and I'm not sure I understand it: every request to the JNDI lookup results in a completely new DataSource being created and filled with connections? Uh, oh. Does that mean that applications should request the DataSource from JNDI a single time during it's life and then re-use that DataSource indefinitely? I'd better stop suggesting that everyone do JNDI lookups every time they need a db connection, then :) - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzlSGQACgkQ9CaO5/Lv0PCC5gCgt9tZul8hmxsIfVYowcHZwrgg SeQAoIKF8X5OrgSxybwCi03C/8uGsesI =6y9U -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: 7.0.4 problem
On 18/11/2010 15:38, Christopher Schultz wrote: Mark, On 11/13/2010 7:26 AM, Mark Thomas wrote: I think you have hit this: https://issues.apache.org/bugzilla/show_bug.cgi?id=50159 Technically, 7.0.4 is sticking to the letter of the J2EE spec but it isn't what applications expect. 7.0.5 will revert to the previous behaviour but with an configurable option for those folks who want their resource factories to behave differently. I've just read that bug description and I'm not sure I understand it: every request to the JNDI lookup results in a completely new DataSource being created and filled with connections? Uh, oh. Does that mean that applications should request the DataSource from JNDI a single time during it's life and then re-use that DataSource indefinitely? I'd better stop suggesting that everyone do JNDI lookups every time they need a db connection, then :) That is what the J2EE spec says (section EE.5.2.4, page 67). By adding the singleton attribute (and defaulting it to true) we can provide the behaviour folks expect, stick to the letter of the J2EE spec and provide folks an option that want the more unusual behaviour. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: 7.0.4 problem
I can confirm my thread issue is fixed in trunk (Revision 1036249) using defaults. -Tony --- Manager, IT Operations Format Dynamics, Inc. P: 303-228-7327 F: 303-228-7305 abia...@formatdynamics.com http://www.formatdynamics.com -Original Message- From: Anthony J. Biacco [mailto:abia...@formatdynamics.com] Sent: Sunday, November 14, 2010 4:54 PM To: Tomcat Users List Subject: RE: 7.0.4 problem Thank you Mark, I'll test with 7.0.5 when it's available and report back. -Tony --- Manager, IT Operations Format Dynamics, Inc. P: 303-228-7327 F: 303-228-7305 abia...@formatdynamics.com http://www.formatdynamics.com -Original Message- From: Mark Thomas [mailto:ma...@apache.org] Sent: Saturday, November 13, 2010 5:27 AM To: Tomcat Users List Subject: Re: 7.0.4 problem On 13/11/2010 00:30, Anthony J. Biacco wrote: Centos 5.5 Linux x64 Mysql connector j 5.1.13 Tomcat 7.0.4 w/apr ajp Mysql cluster 7.1.3 Jdk 1.6.0_21 x64 Anybody aware of any problems with this combination? Using jmeter to load test my servlet, i see mysql threads held up indefinately until i get a 'Too many connections' error from mysql. Ajp threads all go back to Waiting according to visualvm. I have had no such problems with 7.0.2 I think you have hit this: https://issues.apache.org/bugzilla/show_bug.cgi?id=50159 Technically, 7.0.4 is sticking to the letter of the J2EE spec but it isn't what applications expect. 7.0.5 will revert to the previous behaviour but with an configurable option for those folks who want their resource factories to behave differently. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: 7.0.4 problem
Thank you Mark, I'll test with 7.0.5 when it's available and report back. -Tony --- Manager, IT Operations Format Dynamics, Inc. P: 303-228-7327 F: 303-228-7305 abia...@formatdynamics.com http://www.formatdynamics.com -Original Message- From: Mark Thomas [mailto:ma...@apache.org] Sent: Saturday, November 13, 2010 5:27 AM To: Tomcat Users List Subject: Re: 7.0.4 problem On 13/11/2010 00:30, Anthony J. Biacco wrote: Centos 5.5 Linux x64 Mysql connector j 5.1.13 Tomcat 7.0.4 w/apr ajp Mysql cluster 7.1.3 Jdk 1.6.0_21 x64 Anybody aware of any problems with this combination? Using jmeter to load test my servlet, i see mysql threads held up indefinately until i get a 'Too many connections' error from mysql. Ajp threads all go back to Waiting according to visualvm. I have had no such problems with 7.0.2 I think you have hit this: https://issues.apache.org/bugzilla/show_bug.cgi?id=50159 Technically, 7.0.4 is sticking to the letter of the J2EE spec but it isn't what applications expect. 7.0.5 will revert to the previous behaviour but with an configurable option for those folks who want their resource factories to behave differently. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: 7.0.4 problem
On 13/11/2010 00:30, Anthony J. Biacco wrote: Centos 5.5 Linux x64 Mysql connector j 5.1.13 Tomcat 7.0.4 w/apr ajp Mysql cluster 7.1.3 Jdk 1.6.0_21 x64 Anybody aware of any problems with this combination? Using jmeter to load test my servlet, i see mysql threads held up indefinately until i get a 'Too many connections' error from mysql. Ajp threads all go back to Waiting according to visualvm. I have had no such problems with 7.0.2 I think you have hit this: https://issues.apache.org/bugzilla/show_bug.cgi?id=50159 Technically, 7.0.4 is sticking to the letter of the J2EE spec but it isn't what applications expect. 7.0.5 will revert to the previous behaviour but with an configurable option for those folks who want their resource factories to behave differently. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: 7.0.4 problem
From: Anthony J. Biacco [mailto:abia...@formatdynamics.com] Subject: 7.0.4 problem Using jmeter to load test my servlet, i see mysql threads held up indefinately until i get a 'Too many connections' error from mysql. Can you take a thread dump or three and see what everyone's stuck on? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
