[ http://issues.apache.org/jira/browse/DERBY-1020?page=comments#action_12414806 ]
Kathey Marsden commented on DERBY-1020: --------------------------------------- So in the general case you think that Connection.rollback() should not throw an exception if the database has been shut down? I think an error should be thrown on database access error for rollback() per: ttp://java.sun.com/j2se/1.5.0/docs/api/java/sql/Connection.html#rollback() > 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.1.2.3, 10.1.3.0, 10.3.0.0, 10.2.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
