Hi!
Is it possible, that your application uses many transactions? If you forget to
close this connections - the pool is running out of connections from time to
time. Maybe there is just one unclosed transaction somewhere in your
application. If you have a lot of traffic on your site you can
Hi,
Thank you for replying. I've already checked it, but I'll check it again.
But if so, shoudn't I see openned connection (socket) to the database server
?
I do have many transactions. It is an heavy application. Sometimes work
fine for
one or two days and then crash (stop working), both
But if so, shoudn't I see openned connection (socket) to the
database server
?
Hmm, I'm not sure how the commons-pool is using the connection. In my opinion:
yes there should be a lot of open connections. But I'm not sure about this. You
can test this by increasing the number of max
Hi Eduardo,
we were facing similiar issues with a heavy-load-application and torque 3.2. The application uses four connection
pools and many connections with a lot of concurrent transactions. The stack trace of the exception was the same as
yours. Other torque based applications developed by
