Win a copy of Head First Android this week in the Android forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Rob Spoor
  • Bear Bibeault
Saloon Keepers:
  • Jesse Silverman
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • Al Hobbs
  • salvin francis

tomcat connection problem

 
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Dear Sir:
i got the below qustion:
how can i increase connection count in tomcat or is my program does not release connect?
how to solve it? thanks for helping
--------------------------------------------------------------------------------------------------------
org.logicalcobwebs.proxool.ConnectionPool getConnection
023492 -000095 (15/15/00) - Couldn't get connection because we
are at maximum connection count and there are none available
 
Ranch Hand
Posts: 161
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
if this is a JDBC data source set up into the JNDI namespace, using the context.xml in the webapp (and possibly deployed into conf/Catalina/localhost or something like that).. or maybe it is defined in the conf/server.xml itself, there is an option in the commons-dbcp (what is used to create the JDBC connection pool), to specify maxActive="nnn" where nnn is the maximum active connections allowed.. If this is not set, set it to something like 20 for now, if it is set, try increasing it.

Though usually the problem of running out of JDBC connections is not due to heavy concurrent load, but a problem (e.g. bug) in the application, where connections are obtained but not being released, that is, there is likely no close() being called somewhere inside a finally block, like

 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic