I assume you are using this within a web application on an application server like JBoss or Tomcat - is this correct?
Without knowing your configuration it is difficult to be sure what could be causing the problem.
One thing that occurs to me is that it is also good practice to close QueryResults objects that are returned from OQL queries to release resources - possibly including connections.
http://www.castor.org/javadoc/org/exolab/castor/jdo/QueryResults.html#close()
I hope this helps. If not, could you include a bit more information about how you are using Castor and DBCP together? I successfully use Tyrex and Castor together in Tomcat 4.1 so DBCP should be even easier.
Patrick
Michel Bertrand wrote:
Hi !
I'm using Castor and DBCP in my app and I'm having lots of pool exhausted exceptions. I believe that it happens because I have a lot of processing when
showing my app pages. But I'm sure of closing each Castor DB connection after its use. So, I don't see any reason to the exceptions and another strange
thing is that I have this error many times running the app with one single user.
Did you have any hint ? What should I do in this case ? I have to increase the number of connections avaible at the pool ? Should I configure a waiting time ?
Thanks in advance !
Regards, Michel.
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
