[
https://issues.apache.org/jira/browse/ARTEMIS-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721922#comment-16721922
]
ASF subversion and git services commented on ARTEMIS-2050:
----------------------------------------------------------
Commit 3c3c81720a93e7617fca757dd9df49cd3b590d96 in activemq-artemis's branch
refs/heads/master from JiriOndrusek
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=3c3c817 ]
[ARTEMIS-2050] It is possible to get AMQ224000: Failure in initialisation:
java.lang.NullPointerException during shutdown of backup server with shared
store
> It is possible to get AMQ224000: Failure in initialisation:
> java.lang.NullPointerException during shutdown of backup server with shared
> store
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-2050
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2050
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 1.5.5, 2.7.0
> Reporter: Jiri Ondrusek
> Priority: Major
>
> On system with slower reactions, there could be a NullPointerException in log.
>
> Problem happens during shutdown of backup server during activation (using
> SharedStoreBackupActivation)
> Scenario: live/backup pair with shared store. Live is stopped and then backup
> is stopped before activation is complete. On slower machines, there is a
> possibility, that FailbackChecker is initialized even if cluster connection
> is cleared to null (because of shutting down). This ends with NPE during
> backup shutdown.
> It is possible to simulate it with SharedStoreBackupTest with addition of
> Thread.sleep(500) into begining of
> SharedStoreBackupActivation.startFailbackChecker. Exception can be then seen
> in test output.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
