hi bryan thanks for your reply. i'm pretty shure that it was a hard close. it might be that it would have unlocked the table but i was not patient enough to testing it.
do you know where to set such timeouts on linux/derby? fabian ----- Original Message ----- From: "Bryan Pendleton" <[EMAIL PROTECTED]> To: "Derby Discussion" <derby-user@db.apache.org> Sent: Wednesday, March 21, 2007 5:57 PM Subject: Re: Connection reset > > sometimes i get a Connection reset (i'm also investigating why this > > happens but i think i've found a problem with derby) when calling a > > remote derby db. the connection is closed but the transaction is still > > in progress (see last table at the bottom of the mail). > > I think that a Connection Reset can mean that the client was > terminated abruptly without closing all its Statement and Connection > objects. That is, it just hard-closed the TCP/IP connection without > closing all the JDBC resources first. > > When that happens, I think that the server will eventually figure > out that the connection has been closed, and will abort the > in-progress transaction. I am not sure how long it will take for the > server to figure this out. Perhaps it depends on how the network > is configured. > > Does the behavior that you are seeing differ from this? > > thanks, > > bryan > >
