> > That is just the problem. The JDBCProbe locks the semaphore in checkTime > to let other > threads wait for him to unlock the semaphore. This is required because the > JDBCProbe > needs full control over the busypool. The checkTime method iterates over > the busypool
> and will freak out if the connections in the busypool change. why. what is actualy throwing the Concurrent modification Exception? int's it "just" the iterator that freaks out? the pools are thread safe.. (I think)
