From: victor.savkin <vic...@tr...> - 2011-06-01 20:39:58
|
Hi Nick, Thanks for your reply. You are right, last time I didn't restart my server after changing "connectionTimeoutMillis". After I restarted the database server it started closing idle sessions. However, I was experimenting a bit more and I have one question: 1. I set my connectionTimeoutMillis to 60 seconds. Then I ran my app several times each time leaving an open connection. Each time it took about 90 seconds for luciddb to release my connection. 2. I set my connectionTimeoutMillis to 1 second. Then I ran my app several times each time leaving an open connection. Each time it took about 150 seconds for luciddb to release my connection. I'm not sure why it's happening. Why setting connectionTimeoutMillis to 1 second makes luciddb to keep an idle connection for more than 2 minutes. It's not a problem, it's just a bit confusing. One more time, thank you for your prompt reply. Victor -- View this message in context: http://luciddb-users.1374590.n2.nabble.com/Problems-with-Idle-Connections-tp6424556p6428729.html Sent from the luciddb-users mailing list archive at Nabble.com. |