We see the same error, sporadically, we feel it's caused by load-balancers momentarily directing JMS clients to slaves on initial connect during a master failover situation, at least that's our best guess.
-- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
