db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1020) Network Server treats errors on cleanup of connections as an unexpected error after intentional shutdown of the database/server
Date Sat, 03 Jun 2006 15:50:30 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1020?page=comments#action_12414587 ] 

Bryan Pendleton commented on DERBY-1020:
----------------------------------------

I agree with the basic idea, though I'm not sure why we should need to add
a new method and/or a new flag. It seems like it would be cleaner just to
teach the engine not to throw an exception in this case. From my quick scan
of the stack traces in DERBY-273, we've actually finished all the rollback
processing at the point of the exception, and are just trying to do some
bookkeeping to get the connection ready for the next transaction to start.

But of course there will not be any next transaction on this connection, since
the client is already gone and the database is shut down and we're just
cleaning things up. So throwing an exception about what is logically part
of the "next" transaction seems a bit over-eager to me.

So it seems like the engine could be altered so that, rather than throwing an
exception in this case, it could just quietly leave the connection in the state
of "clean, but cannot be used for any future transactions".

That way, there would be no exceptions thrown, so long as the connection
was never used again.

> Network Server treats errors on cleanup of connections as an unexpected error after intentional
shutdown of the database/server
> -------------------------------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-1020
>          URL: http://issues.apache.org/jira/browse/DERBY-1020
>      Project: Derby
>         Type: Bug

>   Components: Network Server
>     Versions: 10.2.0.0, 10.1.3.0, 10.1.2.3, 10.3.0.0
>     Reporter: Kathey Marsden
>     Priority: Minor

>
> Any exceptions that occur in the rollback and close of connections in Session.close()
are treated as unexpected errors and print to the console.
> Exceptions that occur cleaning up the connection after intentional shutdown are not really
unexpected. 
> The console message can be disconcerting and  intermittent as it depends on time.  It
is the root cause of DERBY-273 and I believe DERBY-803

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message