y
not.
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/NullPointerException-in-AbstractInactivityMonitor-tp4660359p4660410.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
Tim Bish
Sr Software Engineer | RedHat Inc.
t
ink it would have
any impact to enable this for the embedded brokers? It's the central broker
where the error is occurring.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/NullPointerException-in-AbstractInactivityMonitor-tp4660359p4660410.html
Sent from the Acti
age in context:
http://activemq.2283324.n4.nabble.com/NullPointerException-in-AbstractInactivityMonitor-tp4660359p4660373.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Have you tried setting concurrentStoreAndDispatchQueues=false to see if
it has any effect?
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/NullPointerException-in-AbstractInactivityMonitor-tp4660359p4660364.html
> Sent from the ActiveMQ - User mail
oker. If we were doing something like trying to send a null
message, I would expect to see some errors in the embedded broker logs
instead of the central broker log.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/NullPointerException-in-AbstractInactivityMonitor-tp4660359p4
ActiveMQ 5.6
RHEL 5.6
java version "1.6.0_23"
Java(TM) SE Runtime Environment (build 1.6.0_23-b05)
Java HotSpot(TM) 64-Bit Server VM (build 19.0-b09, mixed mode)
thanks!
Michael
--
View this message in context:
http://activemq.2283324.n4.nabble.com/NullPointerException-in-Abstr
