Re: DBCP deadlock

2009-11-14 Thread Marc Logemann
Hi, thanks. Great hint. I always checked the DB server but you really need to check to be sure whats going on. Since i am on Mac OS X, i will need to use "lsof" though. Netstat on BSD is not as powerfull as on linux. --- regards Marc Logemann http://www.logemann.org http://www.l

Re: DBCP deadlock

2009-11-12 Thread Marc Logemann
But in my view, connection leak means, i am not closing SQL connections (apart form the fact that i checked this) but then these connections would be "in use" by the pool and also "in use" by the the server jobs that hold the connections. But thats not the case. The "server jobs" may have

Re: DBCP deadlock

2009-11-12 Thread Marc Logemann
for status informations. C3P0 does a better job here or at least they document how to do it. I am still not sure that i am missing closing connections. Only a fraction of my JDBC calls are "manual", the rest is by ORM. --- regards Marc Logemann http:/

Re: DBCP deadlock

2009-11-12 Thread Marc Logemann
Uh sorry, misread that. Commons-pool is at 1.3. As i said, i am using ivy/maven to resolve that stuff and since i am not explicitely grabbing commons-pool, 1.3 was pushed in because of dependency definition of commons-dhcp 1.2.2 --- regards Marc Logemann http://www.logemann.org http

Re: DBCP deadlock

2009-11-12 Thread Marc Logemann
Uhh forgot mention this. Seems i am using 1.2.2 ... quite old isnt it? I am using Maven Central for JAR management and 1.2.2 is the latest over there. Is there a better repository for Commons-DBCP somewhere? --- regards Marc Logemann http://www.logemann.org http://www.logentis.de Am

DBCP deadlock

2009-11-12 Thread Marc Logemann
runnable "VM Periodic Task Thread" prio=10 tid=0x3ce46800 nid=0x3e30 waiting on condition JNI global references: 2272 Heap PSYoungGen total 52736K, used 39185K [0x38e8, 0x3c98, 0x3c99) eden space 45056K, 85% used [0x38e8,0x3b445030,0x3ba800