From: victor.savkin <vic...@tr...> - 2011-05-31 21:08:25
|
Hi Guys, I really struggle to tackle one problem I have with luciddb. When I don't close connections properly I always receive: 'Cache scratch memory exhausted'. Step to reproduce: 1. Write a small java app querying luciddb. 2. When the app starts kill it, so the connection won't be closed. 3. Repeat steps 1-2 more than expectedConcurrentStatements times. 4. Next time you'll get "Cache scratch memory exhausted". I assume luciddb doesn't release memory allocated to those connections. So I tried to fix it by setting connectionTimeoutMillis = 120000 (2 minutes) hoping that luciddb will recreate the connections. But it didn't help. To make it work I have to restart the database which is unacceptable in production. Could you help me with this situation? Thanks, Victor -- View this message in context: http://luciddb-users.1374590.n2.nabble.com/Problems-with-Idle-Connections-tp6424556p6424556.html Sent from the luciddb-users mailing list archive at Nabble.com. |