Thanks for the hint! Probably the client classpath (outside) jboss contains a wrong jar, i will check it. What about the behavior inside the container? JBossObjectMessage seems to be the right one. After setting JMSCorrelationID the object contains (in debugger) the header property. Any idea, how the information is lost on way to the consument? jbossmq.jar is not in the jboss-classpath (recursive search over whole folder). The JBossMessaging is installed as described in the instructions. Note: MDBs are well running, the problems only occur when using direct jms access. (jms client). markus View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159351#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...