Web Hosting Forum | Lunarpages


*
Welcome, Guest. Please login or register.
Did you miss your activation email?



Login with username, password and session length
May 24, 2012, 11:42:07 AM

Pages: [1]   Go Down
  Print  
Author Topic: ConnectionPool problem w/ MySQL  (Read 311 times)
jfhiller
Space Explorer
***
Offline Offline

Posts: 9


WWW
« on: November 11, 2002, 12:01:00 PM »

I'm using JSP and MySQL to make a simple message board.  I have a Connection pool that works well on my Tomcat localhost installation.  On my machine, I put the connection pool and other classes that I intend to use for multiple webapps in the classes directory immediately under the tomcat home directory.  Since there doesn't appear to be an analogous directory in Resin, I put the connection pool class in the WEB-INF/classes directory of my only lunarpages webapp.  

Here's the problem:  When I upload the connection pool classes, the connections seem to work for a short time.  However, it appears the they soon stop functioning.  

I'm confident that the class is good b/c I've used it successfully for a long time and the only thing I changed was the DB, user, pwd in the mm.mysql string.  Could the initial instantiation be dying somehow?  I have to restart Tomcat each time I change a class, so I'm wondering if the differences with Resin are contributing to the problem.  

Another related question:  is there a "super" classes directory in Resin like there is with Tomcat?  I tried creating a classes directory under public_html, but it didn't seem to have the same effect.  

I'm planning to install Resin on my machine in the near future, but in the meantime, any help would be greatly appreciated as I'm at a complete loss for ideas.  (Sorry this is so long...)
Logged
jfhiller
Space Explorer
***
Offline Offline

Posts: 9


WWW
« Reply #1 on: November 18, 2002, 03:53:00 AM »

After reading on the topic, I found the following bit regarding Resin DB connection pools.  I think this is why my Connections in my connection pool were dying.  I thought it might be helpful for others with the same problem:

max-connections
Maximum number of allowed connections - 20

max-idle-time
Maximum time an idle connection is kept in the pool - 30 sec

max-active-time
Maximum time a connection allowed to be active - 6 hours

max-pool-time
Maximum time a connection is kept in the pool - 24 hours

connection-wait-time
How long to wait for an idle connection (Resin 1.2.3) - 10 minutes

max-overflow-connections
How many "overflow" connection are allowed if the connection wait times out. - 0
 
 [ November 18, 2002, 11:54 AM: Message edited by: jfhiller ]
Logged
stephan
Guest
« Reply #2 on: November 18, 2002, 09:42:00 AM »

I'm pleased you got it fixed.
Logged
Pages: [1]   Go Up
  Print  
 
Jump to: