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