No Tim, there are no more stack traces. Maybe the implementation of
TopicMessageStore.recoverNextMessages() just throws a new ClassCastException
?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ClassCastException-while-subscribing-to-a-topic-tp4710870p4711256.html
Sent
Is there no "caused by" stack trace immediately after what you quoted? The
exception is a ClassCastException wrapped in a RuntimeException; you've
given us the stack trace for the outer RuntimeException, but the stack
trace for the inner ClassCastException is the more useful of the two.
Tim
On
When you say "the web console refuses all connections," do you mean it
allows you to provide a username and password but doesn't authorize access
for any of the username/password pairs you set up as described in
http://activemq.apache.org/web-console.html? Or something else?
On Apr 25, 2016
Cross-datacenter connectivity is definitely possible.
You can configure ActiveMQ to discard messages once the dispatch queue is
full, and you can specify strategies for deciding which messages to
discard, but it appears that you're already using them so maybe you're
looking for something
Hi,
I’m trying to figure out why my activemq 5.13.2 broker logging lot of WARN
-s
“Invalid log position…”
2016-04-26 04:35:40,085 | WARN | Invalid log position: 8434 |
org.apache.activemq.leveldb.LevelDBClient | Thread-2
2016-04-26 04:35:44,260 | WARN | Invalid log position: 8498 |
