Re: [luciddb-users] Problems with Idle Connections

[Nicholas G. <ngo...@dy...>]

My best guess: vJDBC (which is our client server protocol for remote connections) does have a "ping" over HTTP to keep it open.  My best guess (I haven't looked into this code for ages so it's a guess) is that vJDBC might have it's own timer thread that runs to mark connections as stale (and after we get the vJDBC notification is when we mark it as unused).

I'm not sure we've ever noticed this as typically the connection time out for most BI / DW workloads is usually 20, 30, 60 min - ish.  If the vJDBC timer is 30 or 60 seconds itself this could make a big difference (as you noted) in smaller times.

Nick

On Jun 1, 2011, at 1:39 PM, victor.savkin wrote:

> 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.