You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by jack patwork <jr...@gmail.com> on 2016/12/02 13:40:14 UTC

Re: 5.14.1 Upgrade causes Failed to browse Topic NullPointerException

Looks like this wasn't a clean shutdown. There were still clients connected
and consuming from the topics and queues. Not sure if that could have
caused the warnings I posted.

After ensuring the client activity had also stopped I was able to do a
clean update without seeing this problem.

Regards,

Jack

On 30 November 2016 at 14:08, Tim Bain <tb...@alumni.duke.edu> wrote:

> Is it possible that the index got left behind even though the log files got
> deleted?
>
> On Nov 30, 2016 5:25 AM, "Christopher Shannon" <
> christopher.l.shannon@gmail.com> wrote:
>
> > Can you post your broker configuration?  This seems odd that would happen
> > if you removed the db.
> >
> > On Wed, Nov 30, 2016 at 5:04 AM, jack patwork <jr...@gmail.com>
> > wrote:
> >
> > > Hi,
> > >
> > >
> > > 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.
> FixedCountSubscriptionRecovery
> > > Policy.browse(FixedCountSubscriptionRecoveryPolicy.java:102)
> > > [activemq-broker-5.14.1.jar:5.14.1]
> > > at
> > > org.apache.activemq.broker.region.policy.
> RetainedMessageSubscriptionRec
> > > overyPolicy.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]
> > >
> > >
> > > Thanks in advance for any help on this,
> > >
> > > Jack
> > >
> >
>