I dont think so, I doubt youll get much help there.....does it ALWAYS happen or just sometimes? The reason I mention that is that we have gotten this exception before with a spring based JMS listeners trying to connect to a TCP AMQ broker URL and both were AMQ 4.1.1 out of the box. However, it was not reproduceable regularly. Never got any 100% as to why it happens, seemed to be related to load sometimes, other times no ideas.
All the client and server jars are from the ActveMQ installation. Disabling the firewall has no effect on the problem. I've written a test JMS app that produces and consumes an ObjectMessage in the topic which works just fine. Maybe this should be posted in a log4j forum. -- View this message in context: http://www.nabble.com/ActiveMQ-5-and-Log4j-JMSAppender-error-tp14622389s2354p14652869.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
