Actually, what also works is to not use a rar (just use a providerloader) but still create a new message on the target session. Please note that the class throwing the exception is JBossMessage on the setDestination...if the spec claims that 1.1 compliant providers should allow foreign messages doesn't this really mean that it is JBM that is not compliant? ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053839#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...