You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Christopher L. Shannon (JIRA)" <ji...@apache.org> on 2016/04/14 20:43:25 UTC

[jira] [Updated] (AMQ-6250) MultiKahaDBTransactionStore should have null protection in close

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

Christopher L. Shannon updated AMQ-6250:
----------------------------------------
    Fix Version/s: 5.13.3

> MultiKahaDBTransactionStore should have null protection in close
> ----------------------------------------------------------------
>
>                 Key: AMQ-6250
>                 URL: https://issues.apache.org/jira/browse/AMQ-6250
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: KahaDB
>    Affects Versions: 5.9.1, 5.13.2
>            Reporter: james
>            Assignee: Christopher L. Shannon
>            Priority: Minor
>             Fix For: 5.14.0, 5.13.3
>
>
> When utilizing the MultiKahaDBPersistenceAdapter and there is a failure during broker startup, (depending on when the startup failure occurs) a secondary NullPointerException can be generated from MultiKahaDBTransactionStore.close.  this happens if the transaction store is closed when it has not yet been opened.  the problem is that the close method does not check the journal for null before closing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)