Page 1 of 1

Connection pooling trace

Posted: 25 Jan 2013, 15:28
by Neznajka
there is option to get connection
getParentExtension().getParentZone().getDBManager().getConnection();

it would be great to add trace if all connections are busy.

sometimes somewhere you forget to close connection and than server just don't work when this function is called in my case 10 times. at least for me it takes long time to understand what is wrong, couse of this problem is that you don't see where is the problem. if there would be some message trace or something to know that all connections are busy, there would be much easier to understand where is the problem.

Re: Connection pooling trace

Posted: 27 Jan 2013, 23:56
by rjgtav
Hi,

Currently there's a bug on the current release (2.5.0), where it was supposed to thrown an exception when the pool is full, but currently it isn't.
Stay tuned for the next update, coming this week probably, which already fixes this issue.

Thanks