db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-5087) NPE in istat daemon when encountering critical exception during shutdown
Date Wed, 02 Mar 2011 22:55:38 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kristian Waagan updated DERBY-5087:
-----------------------------------

    Attachment: derby-5087-1a-npe_on_shutdown.diff

Attaching patch 1a, which removes the possibility of the NPE.
Also removed unnecessary variable 'daemonStopped', replacing it with 'daemonDisabled' where
used.

Committed to trunk with revision 1076445.

> NPE in istat daemon when encountering critical exception during shutdown
> ------------------------------------------------------------------------
>
>                 Key: DERBY-5087
>                 URL: https://issues.apache.org/jira/browse/DERBY-5087
>             Project: Derby
>          Issue Type: Bug
>          Components: Services, Store
>    Affects Versions: 10.8.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>         Attachments: derby-5087-1a-npe_on_shutdown.diff
>
>
> If the istat daemon encounters a critical error during shutdown and the data dictionary
module has been stopped, it will run into a NPE.
> This bug is highly timing-dependent in two ways: the data dictionary module must have
been stopped first, and then the istat daemon must encounter a critical error "at the right
time".
> I have seen this bug once on my laptop.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message