db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-4871) FileContainer should log StandardException seen inside doPreAllocatePages
Date Thu, 28 Oct 2010 00:32:21 GMT
FileContainer should log StandardException seen inside doPreAllocatePages

                 Key: DERBY-4871
                 URL: https://issues.apache.org/jira/browse/DERBY-4871
             Project: Derby
          Issue Type: Improvement
          Components: Store
            Reporter: Dag H. Wanvik

In FileContainer#doPreAllocatePages we find this snippet:

catch (StandardException se)
  // if something went wrong, stop and return how many we did
  // successfully 
  error = true;

In my case I was debugging interrupts and this was the first error
Derby saw. However, since it's swallowed, we never see in derby.log
what happened.

In my case, I saw a subsequent ChannelClosedException as the (next)
error which was unexpected since that should only occur as a secondary
thing after a ClosedByInterruptException, and the
ClosedByInterruptException was not manifest anywhere.

So, although DERBY-4741 should make this particular event less likely
(by retrying after interrupts), it would be nice to log errors seen
here to derby.log.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message