This is known bug in Jboss fuse 6.1 and the issue is fixed in JBoss Fuse 6.1
R2P5 rollup patch5. 



--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Reply via email to