Can a connection expire?

[Barnet Wagman <b....@comcast.net>]

Can a connection expire in an embedded Derby system?  I got a 'SQL 
Exception: No current connection.' exception in the middle of a series 
of inserts.  The vm was still running after the exception.  I didn't see 
anything about timeout or idle time in the manuals.

FYI I reuse a PreparedStatements extensively, but that's never been a 
problem in the past.

Thanks,

bw

Re: Can a connection expire?

[Barnet Wagman <b....@comcast.net>]

Satheesh Bandaram wrote:

>I don't think a connection expires in embedded Derby.  Could it be
>possible a severe error was encountered during the INSERTs that might
>have caused the connection to close? Was there any info in the
>derby.log? This log file should get created in the SYSTEM_HOME location.
>
>  
>
I think your right, something appears to be causing the connection to 
close, but there's nothing in my log file.  Actually, I can't find a 
derby.log file at all.  By default, it SYSTEM_HOME the directory where 
the database resides?  I was using vanilla installation of embedded 
Derby. I've tried recreating the database with logDevice explicitly set, 
but I'm still not getting a derby.log file.  Do I need to do something 
explicit to get one?

Thanks

Re: Can a connection expire?

[Satheesh Bandaram <sa...@Sourcery.Org>]

I don't think a connection expires in embedded Derby.  Could it be
possible a severe error was encountered during the INSERTs that might
have caused the connection to close? Was there any info in the
derby.log? This log file should get created in the SYSTEM_HOME location.

Satheesh

Barnet Wagman wrote:

> Can a connection expire in an embedded Derby system?  I got a 'SQL
> Exception: No current connection.' exception in the middle of a series
> of inserts.  The vm was still running after the exception.  I didn't
> see anything about timeout or idle time in the manuals.
>
> FYI I reuse a PreparedStatements extensively, but that's never been a
> problem in the past.
>
> Thanks,
>
> bw
>
>