tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Graham Leggett <>
Subject Tomcat v4.1.27 with database pools unreliable
Date Sun, 08 Feb 2004 11:31:34 GMT
Hi all,

I have been using tomcat v4.1.27 for a while, hosting some web 
applications without any notable reliability hassles.

Along comes a new application - this app uses the database pool feature 
of tomcat. While this application is deployed, tomcat refuses to stay 
operational for more than an hour or two at a time. After a few hours, 
attempts to connect to tomcat via the HTTP connector hang. Sometimes, 
tomcat unbinds itself from the listening port, causing "connection 
refused" errors to the client - but tomcat itself still stays resident.

Nothing meningful is logged in any logfile.

What are my options? Did the jump from v4.1.27 to v4.1.29 fix anything 
reliability wise? Or should I try and upgrade the server to Tomcat v5 

Is the tomcat database pool feature something that should be used in 

The database config in the config file looks like this:

     <Resource name="jdbc/GlobalPatricia" auth="Container"
     <ResourceParams name="jdbc/GlobalPatricia">


The web application context xml definition looks like this:

<Context path="/patricia" docBase="patricia" >

   <Valve className="org.apache.catalina.valves.RemoteAddrValve"

   <Logger className="org.apache.catalina.logger.FileLogger"
              prefix="localhost_patricia_log." suffix=".txt"

   <ResourceLink name="jdbc/GlobalPatricia" global="jdbc/GlobalPatricia" 

   <Realm className="org.apache.catalina.realm.DataSourceRealm" debug="0"
     userTable="person" userNameCol="uid" userCredCol="user_password"
     userRoleTable="company_person" roleNameCol="serial"/>



To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message