On 4/12/2015 5:18 AM, Kristian Rosenvold wrote: > I once had a library that allocated 2 connections to complete a > transaction. Every now and then we'd deadlock the pool if number of > concurrent transactions > pool size, which could happen in load > bursts. If you do a thread dump of your process and see "all" threads > are waiting for a connection this is most probably happening. The > non-solution solution is to increase pool size, the real solution was > never to allocate 2 connections to complete a transaction.
It will take a code review to be sure, but I'm pretty sure I would remember if there was anything odd like that in the code. Thanks, Shawn --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
