RE: Re: Re: Re: Re: Re: Re: Re: Re: Re: Another Try at MySQL Connection Pooling

2004-02-12 Thread Shapira, Yoav
Curwen [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 11, 2004 6:22 PM To: 'Tomcat Users List' Subject: RE: Re: Re: Re: Re: Re: Re: Re: Re: Re: Another Try at MySQL Connection Pooling comicbook-guy Stupidest auto-responder *EVER* /comicbook-guy -Original Message- From: [EMAIL

Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread David Smith
I'm using this setup on a linux box and the only thing I can see different is your URL. I'm not familiar with the named pipes method of accessing MySQL from Tomcat. My URL is of this format: jdbc:mysql://[server name]:3306/[database name]?autoReconnect=true Also, did you place the

RE: Another Try at MySQL Connection Pooling

2004-02-11 Thread Burgess, Jay S
offline and I'd be happy to forward it to you as well. Let us know how it progresses. Jay -Original Message- From: David Smith [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 11, 2004 8:03 AM To: Tomcat Users List Subject: Re: Another Try at MySQL Connection Pooling I'm using this setup

RE: Another Try at MySQL Connection Pooling

2004-02-11 Thread Burgess, Jay S
Oops. Haven't had my coffee yet. I read MySQL but thought SQL Server. Obviously my DB is different than yours, so that may explain our differences. But either way, my previous post might still help. Jay -Original Message- From: Merrill Cornish [mailto:[EMAIL PROTECTED] Sent:

RE: Another Try at MySQL Connection Pooling

2004-02-11 Thread Merrill Cornish
Jay, Thanks for your comments. I think the problem may be that I don't have the MySQL Connector/J jar in the common/lib. When using DriverManager, it worked fine in jre/lib/ext, which is one of the places the MySQL documentation recommended. I need to try again with it in the new location.

RE: Another Try at MySQL Connection Pooling

2004-02-11 Thread Yiannis Mavroukakis
As far as the listening bit is concerned why not just limit mySQL to listen on localhost then? Do you get better performance out of named pipes? -Original Message- From: Merrill Cornish [mailto:[EMAIL PROTECTED] Sent: 11 February 2004 15:52 To: Tomcat Users List Subject: RE: Another Try

Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread Mark Matthews
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Yiannis Mavroukakis wrote: As far as the listening bit is concerned why not just limit mySQL to listen on localhost then? Do you get better performance out of named pipes? On most versions of Windows, using JDBC and MySQL with named pipes will

Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread Philipp Taprogge
Hi! Mark Matthews wrote: On most versions of Windows, using JDBC and MySQL with named pipes will give you a 50-60% performance improvement. Which IMO is by no way an intidator of Win's greatness in named pipes but rather of it's bad TCP implementation. Instead of relying on named pipes one

RE: Another Try at MySQL Connection Pooling

2004-02-11 Thread Yiannis Mavroukakis
I'll add another 2 to the pool :) -Original Message- From: Philipp Taprogge [mailto:[EMAIL PROTECTED] Sent: 11 February 2004 16:24 To: Tomcat Users List Subject: Re: Another Try at MySQL Connection Pooling Hi! Mark Matthews wrote: On most versions of Windows, using JDBC and MySQL

RE: Another Try at MySQL Connection Pooling

2004-02-11 Thread Merrill Cornish
I think I read the using named pipes is faster, but that's not going to be a problem here. If I can't get named pipes to work, then I'll try using TCP/IP restricted to localhost. Actually, this whole DataSource experiment has a questionable return on investment. I already have it working

Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread Merrill Cornish
David, I THINK I've figure out that MySQL's Connector/J jar worked in jre/lib/ex when I was using DriverManager because only MySQL needed to see it, and it knew to look in jre/lib/ex. However, with DataSource, I'm assuming it's Tomcat who needs to see it, so it needs to be in Tomcat's

RE: Another Try at MySQL Connection Pooling

2004-02-11 Thread Januski, Ken
Merrill, Much of what you're doing is just beyond me but I can't help but noticing this in your first post. parameter namepassword/name valuexxx/value /parameter Since you've included a password value in all the other places I'm wondering if the lack of it here could be

RE: Another Try at MySQL Connection Pooling

2004-02-11 Thread Burgess, Jay S
) envContext.lookup(jdbc/TimesheetsDB ); Just a thought, in case you've got one of the strings wrong. Jay -Original Message- From: Merrill Cornish [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 11, 2004 11:43 AM To: Tomcat Users List Subject: Re: Another Try at MySQL Connection Pooling

Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread Parsons Technical Services
: Wednesday, February 11, 2004 12:43 PM Subject: Re: Another Try at MySQL Connection Pooling David, I THINK I've figure out that MySQL's Connector/J jar worked in jre/lib/ex when I was using DriverManager because only MySQL needed to see it, and it knew to look in jre/lib/ex. However, with DataSource

Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread Mark Matthews
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Parsons Technical Services wrote: Merrill, I may end up eating a little sole, but I have had shoe before. Your name for the jdbc is wrong. It should be: !-- Class name for mm.mysql JDBC driver -- parameter namedriverClassName/name

RE: Another Try at MySQL Connection Pooling

2004-02-11 Thread Merrill Cornish
Jay, Context initialContext = new InitialContext(); Context envContext = (Context) initialContext.lookup(java:comp/env); this.dataSource = (DataSource) envContext.lookup(jdbc/TimesheetsDB ); Ah ha! I was missing the second step. When I added the second step, it still fails, but the

Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread Merrill Cornish
Doug, I noticed the class name discrepancy myself between the name I had used for DriverManager and the one the DataSource example had. However, when I peeked inside the Connector/J jar file, I found both .class files, altough they are of different sizes. I tried it with your alternative,

Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread Parsons Technical Services
[EMAIL PROTECTED] Cc: Merrill Cornish [EMAIL PROTECTED] Sent: Wednesday, February 11, 2004 2:33 PM Subject: Re: Another Try at MySQL Connection Pooling -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Parsons Technical Services wrote: Merrill, I may end up eating a little sole, but I have

RE: Another Try at MySQL Connection Pooling

2004-02-11 Thread Merrill Cornish
Ken, I didn't intend to include the password in ANY of my posts, but I guess some slipped though. In the version that running, the password is there. And, even if I had fumble fingered the password, THAT would have simply gotten a convention MySQL error rather than a NameNotFoundException

RE: Another Try at MySQL Connection Pooling

2004-02-11 Thread Burgess, Jay S
To: Tomcat Users List Subject: RE: Another Try at MySQL Connection Pooling Jay, Context initialContext = new InitialContext(); Context envContext = (Context) initialContext.lookup(java:comp/env); this.dataSource = (DataSource) envContext.lookup(jdbc/TimesheetsDB ); Ah ha! I was missing

Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread Parsons Technical Services
[EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, February 11, 2004 2:27 PM Subject: RE: Another Try at MySQL Connection Pooling Ken, I didn't intend to include the password in ANY of my posts, but I guess some slipped though. In the version that running, the password

Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread Adam Hardy
, then this could be an issue. Probably not, but worth mentioning, just in case. Jay -Original Message- From: Merrill Cornish [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 11, 2004 2:04 PM To: Tomcat Users List Subject: RE: Another Try at MySQL Connection Pooling Jay, Context initialContext

Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread Merrill Cornish
Doug, Timesheet vs. timesheet Good catch, but it didn't make any difference. I originally had three Context entries for names Timesheet, (the way I thought of it), timesheet (for those who don't want to use the shift key), and ts (for those diehard Unix freaks who believe anything

Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread Merrill Cornish
Adam, The following line occurs in stdout.log: INFO: Processing Context configuration file URL file:C:\Program Files\Apache Group\Tomcat 5.0.18\conf\Catalina\localhost\timesheet.xml so it appears to be getting the correct context fragment. Merrill

Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread Adam Hardy
On 02/11/2004 10:15 PM Merrill Cornish wrote: Adam, The following line occurs in stdout.log: INFO: Processing Context configuration file URL file:C:\Program Files\Apache Group\Tomcat 5.0.18\conf\Catalina\localhost\timesheet.xml so it appears to be getting the correct context fragment. What if

Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread Parsons Technical Services
just say I'm shiny on top and little things like this didn't help. Doug Parsons www.parsonstechnical.com - Original Message - From: Adam Hardy [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, February 11, 2004 4:30 PM Subject: Re: Another Try at MySQL Connection

Re: Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread correo
Ya hemos recibido su solicitud de correo en breve le enviaremos su nombre de usuario y contreseña. Gracias por confiar en nosotros - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Re: Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread correo
Ya hemos recibido su solicitud de correo en breve le enviaremos su nombre de usuario y contreseña. Gracias por confiar en nosotros - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Re: Re: Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread correo
Ya hemos recibido su solicitud de correo en breve le enviaremos su nombre de usuario y contreseña. Gracias por confiar en nosotros - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Re: Re: Re: Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread correo
Ya hemos recibido su solicitud de correo en breve le enviaremos su nombre de usuario y contreseña. Gracias por confiar en nosotros - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Re: Re: Re: Re: Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread correo
Ya hemos recibido su solicitud de correo en breve le enviaremos su nombre de usuario y contreseña. Gracias por confiar en nosotros - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Re: Re: Re: Re: Re: Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread correo
Ya hemos recibido su solicitud de correo en breve le enviaremos su nombre de usuario y contreseña. Gracias por confiar en nosotros - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Re: Re: Re: Re: Re: Re: Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread correo
Ya hemos recibido su solicitud de correo en breve le enviaremos su nombre de usuario y contreseña. Gracias por confiar en nosotros - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

RE: Re: Re: Re: Re: Re: Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread Parker, Matt
auto-reply sucks for mailing lists... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 11, 2004 4:11 PM To: [EMAIL PROTECTED] Subject: Re: Re: Re: Re: Re: Re: Re: Another Try at MySQL Connection Pooling Ya hemos recibido su

Re: Re: Re: Re: Re: Re: Re: Re: Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread correo
Ya hemos recibido su solicitud de correo en breve le enviaremos su nombre de usuario y contreseña. Gracias por confiar en nosotros - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: RE: Re: Re: Re: Re: Re: Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread correo
Ya hemos recibido su solicitud de correo en breve le enviaremos su nombre de usuario y contreseña. Gracias por confiar en nosotros - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread correo
Ya hemos recibido su solicitud de correo en breve le enviaremos su nombre de usuario y contreseña. Gracias por confiar en nosotros - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

RE: Another Try at MySQL Connection Pooling

2004-02-11 Thread Burgess, Jay S
Message- From: Parsons Technical Services [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 11, 2004 3:56 PM To: Tomcat Users List Subject: Re: Another Try at MySQL Connection Pooling Merrill, Humor me for a moment. This might be due to you trying different setups, but, take a minute to go

Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread Merrill Cornish
Doug, The application directory under webapps is named timesheet, therefore, the context fragment in conf/Catalina/localhost is timesheet.xml to match the context name. The beginning of the Context element in timesheet.xml is Context path=/timesheet docBase=timesheet . . . to match the

RE: Another Try at MySQL Connection Pooling

2004-02-11 Thread Merrill Cornish
Jay, once in my .WAR, and once as a result of my Ant deploy task I have yet to move to that plane of confusion. I'm not using a META-INF directory or a .WAR file since I'm still trying to figure out WHAT to deploy. I am manually editing * the conf/server.xml file (to change the

RE: Another Try at MySQL Connection Pooling

2004-02-11 Thread Kenneth
Well, it's not that I'm an expert... I actually have had that problem once or twice, and most of the time the problem was in the context.xml I've always specified my webapps' Context in a separated file (which I believe you're also doing), but when I messed up with server.xml I had some

Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread Parsons Technical Services
a copy of my files. Two differences: I am on linux and 4.1.29. - Original Message - From: Merrill Cornish [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, February 11, 2004 5:34 PM Subject: RE: Another Try at MySQL Connection Pooling Jay, once in my .WAR

Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread Adam Hardy
Merrill, I think everyone's waiting to see you kick yourself when you discover what the problem is... ;) No seriously, there are 2 things that I would try - (1) debug the context - I think it returns an enum of entries available from some method, and (2) go back to the most basic test servlet

RE: Re: Re: Re: Re: Re: Re: Re: Re: Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread Mike Curwen
comicbook-guy Stupidest auto-responder *EVER* /comicbook-guy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 11, 2004 5:15 PM To: [EMAIL PROTECTED] Subject: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Another Try at MySQL

Re: Another Try at MySQL Connection Pooling

2004-02-11 Thread SMaric
This is what works for me - (see NOTES at end - if anyone can shed any light on Limiting Pool size) #1in your Server.xml GlobalNamingResources Resource name=MySQLDataSourceFactory type=com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource auth=Container/ ResourceParams