It doesn't, it throws a new RuntimeException wrapping the inner exception, and I've never seen Log4J not lot the inner exception's stack trace. Too bad, because without knowing where that ClassCastException was thrown, it's likely to be difficult to impossible to fix the problem. On Apr 26, 2016 10:01 PM, "Shobhana" <shobh...@quickride.in> wrote:
> 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 from the ActiveMQ - User mailing list archive at Nabble.com. >
