[
https://issues.apache.org/jira/browse/AMQ-6250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15241700#comment-15241700
]
ASF subversion and git services commented on AMQ-6250:
------------------------------------------------------
Commit 61dc6888045544cbaad6b4ea5a3302b3f23fe4d3 in activemq's branch
refs/heads/activemq-5.13.x from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=61dc688 ]
https://issues.apache.org/jira/browse/AMQ-6250
Checking for null before closing the journal in
MultiKahaDBPersistentAdapter. Also protecting against multiple calls to
start and stop.
> 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
>
>
> 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)
