-
Bug
-
Resolution: Done
-
Major
-
JBoss A-MQ 6.2.1
-
None
-
None
The broker logs are filling with the following messages:
00:45:03,002 | WARN | r[amq] Scheduler | AdvisoryBroker | 185 - org.apache.activemq.activemq-osgi - 5.11.0.redhat-621090 | Failed to fire expired advisory, reason: java.lang.NullPointerException 00:45:03,002 | WARN | r[amq] Scheduler | AdvisoryBroker | 185 - org.apache.activemq.activemq-osgi - 5.11.0.redhat-621090 | Failed to fire expired advisory, reason: java.lang.NullPointerException 00:45:03,002 | WARN | r[amq] Scheduler | AdvisoryBroker | 185 - org.apache.activemq.activemq-osgi - 5.11.0.redhat-621090 | Failed to fire expired advisory, reason: java.lang.NullPointerException 00:45:03,003 | WARN | r[amq] Scheduler | AdvisoryBroker | 185 - org.apache.activemq.activemq-osgi - 5.11.0.redhat-621090 | Failed to fire expired advisory, reason: java.lang.NullPointerException 00:45:03,003 | WARN | r[amq] Scheduler | AdvisoryBroker | 185 - org.apache.activemq.activemq-osgi - 5.11.0.redhat-621090 | Failed to fire expired advisory, reason: java.lang.NullPointerException 00:45:03,003 | WARN | r[amq] Scheduler | AdvisoryBroker | 185 - org.apache.activemq.activemq-osgi - 5.11.0.redhat-621090 | Failed to fire expired advisory, reason: java.lang.NullPointerException 00:45:03,003 | WARN | r[amq] Scheduler | AdvisoryBroker | 185 - org.apache.activemq.activemq-osgi - 5.11.0.redhat-621090 | Failed to fire expired advisory, reason: java.lang.NullPointerException
This is causing broker logs to roll more frequently than desired.
