You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "jack patwork (JIRA)" <ji...@apache.org> on 2016/11/30 10:02:59 UTC
[jira] [Resolved] (AMQ-6523) 5.14.1 Upgrade causes Failed to browse
Topic NullPointerException
[ https://issues.apache.org/jira/browse/AMQ-6523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jack patwork resolved AMQ-6523.
-------------------------------
Resolution: Invalid
> 5.14.1 Upgrade causes Failed to browse Topic NullPointerException
> -----------------------------------------------------------------
>
> Key: AMQ-6523
> URL: https://issues.apache.org/jira/browse/AMQ-6523
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.14.1
> Environment: Centos 5.5
> Reporter: jack patwork
>
> After upgrading a 4 node cluster from 5.9.1 to 5.14.1 I'm seeing my amq logs spammed with 1000's of the following warnings. This was after shutting down all 4 instances, deleting the db and restarting them.
> It looks like the scheduler is stuck in a loop trying to deal with topics that have been deleted. I'm just wondering where the scheduler has picked up these tasks from given that the db was completely removed.
> 2016-11-29 15:14:55,555 | WARN | Failed to browse Topic: my.custom.topic.123 | org.apache.activemq.broker.region.Topic | ActiveMQ Broker[myBrokerName] Scheduler
> java.lang.NullPointerException
> at org.apache.activemq.broker.region.policy.FixedCountSubscriptionRecoveryPolicy.browse(FixedCountSubscriptionRecoveryPolicy.java:102)[activemq-broker-5.14.1.jar:5.14.1]
> at org.apache.activemq.broker.region.policy.RetainedMessageSubscriptionRecoveryPolicy.browse(RetainedMessageSubscriptionRecoveryPolicy.java:111)[activemq-broker-5.14.1.jar:5.14.1]
> at org.apache.activemq.broker.region.Topic.doBrowse(Topic.java:674)[activemq-broker-5.14.1.jar:5.14.1]
> at org.apache.activemq.broker.region.Topic.access$100(Topic.java:69)[activemq-broker-5.14.1.jar:5.14.1]
> at org.apache.activemq.broker.region.Topic$6.run(Topic.java:780)[activemq-broker-5.14.1.jar:5.14.1]
> at org.apache.activemq.thread.SchedulerTimerTask.run(SchedulerTimerTask.java:33)[activemq-client-5.14.1.jar:5.14.1]
> at java.util.TimerThread.mainLoop(Timer.java:555)[:1.7.0_101]
> at java.util.TimerThread.run(Timer.java:505)[:1.7.0_101]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)