On Fri, Sep 21, 2012 at 3:27 PM, Gemoets, Darren <darren.gemo...@aquilent.com> wrote: > Hello, all. I have a simple test program that opens a JDBC connection to a > PostgreSQL database (using the Tomcat connection pool) and runs a simple > query. It uses connection/result closing code from the documentation. The > test program works fine standalone, but when I use it via an Axis2 web > service, it seems to be causing abandoned connections. After a few > connections, it can’t connect because there are no connections available > because they’re all abandoned. > > > > I haven’t done anything fancy with the service, the WSDL, the transport, or > anything...in poking around I see some things that maybe look related like > REUSE_HTTP_CLIENT and I also ran across this entry from StackOverflow > (http://stackoverflow.com/questions/1093888/how-can-i-test-if-my-connection-pool-is-working-in-a-correct-way) > that could be relevant, though not for the novice Axis2 user. > > > > Any thoughts? Any more info needed? > > > > Thank you.
Offtopic ... but you sure seem like you are somehow not executing close() on your db connections. Hard to see how axis2 is part of the problem without logs, stacktraces or code. Standalone would shut down the pool so you might have glossed over some close() issue. - R --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org For additional commands, e-mail: java-user-h...@axis.apache.org
