| guest |
Wed May 27 16:36:04 BST 2009 |
| |
Hi,
we came upon scenario:
0. KillActiveConnectionsOverAge - set to 2 mins
1. Connection starts doing long query (e.g. 5 mins)
2. Pool is working correctly for 2 mins
3. PoolMonitor - grabs the connection and tries to do:
107: ch.conn.closePhysical();
4. as start of this block is synchronized (pool.lock) - no other connections can be granted
5. Unfortunately step 3. lasts 5 mins - resulting in unnecessary blocking complete pool for 3 minutes
Regards,
Neb
|
| |
| sedj |
Wed May 27 19:59:55 BST 2009 |
| |
Hi,
We fixed this bug last month, but are still testing it. If you want a preview of the next release, use the "Contact Us" page to mail me, and I'll send you the next version.
Hope to release it officially in the next few weeks. |
| ScottO |
Tue Jun 23 14:15:24 BST 2009 |
| |
Hi Sedj,
That is good news with this fix.
Do you have an update as to when you think the next release will be available?
Thanks,
Scott
|
| sedj |
Sun Jul 26 16:27:35 BST 2009 |
| |
| Finally released, sorry about the delay ! |
| Scott O. |
Mon Aug 24 19:43:26 BST 2009 |
| |
Great. Thanks Sedj. Ever think of creating a mail list to send notifications when news comes out... such as even a new app...open source of not?
- Scott |
|
