Anyway, it would be easy to make a small code change to workaround the ActiveMQ behaviour. I don't have ActiveMQ set up here, so maybe you could try this: Remove this code from JBossMessage::setDestination() | if (!(destination instanceof JBossDestination)) | { | throw new InvalidDestinationException("Destination cannot be foreign"); | } | Also we should probably add a sanity check in ProducerAspect::handleSend() to check if the destination is actually a JBossDestination, in case someone is actually stupid enough to try and send a message to JBM with a foreign destination set. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053842#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...