I now getting this exception | 2007-12-07 12:20:42,534 WARN [org.jboss.jms.server.bridge.Bridge] Failed to send + acknowledge batch, closing JMS objects | javax.jms.JMSException: Can only set JMSXGroupId, JMSXGroupSeq, JMSXDeliveryCount | at org.jboss.jms.message.JBossMessage.checkProperty(JBossMessage.java:1102) | at org.jboss.jms.message.JBossMessage.setObjectProperty(JBossMessage.java:916) | at org.jboss.jms.message.JBossMessage.<init>(JBossMessage.java:365) | at org.jboss.jms.message.JBossObjectMessage.<init>(JBossObjectMessage.java:94) | at org.jboss.jms.client.container.ProducerAspect.handleSend(ProducerAspect.java:197) | at org.jboss.aop.advice.org.jboss.jms.client.container.ProducerAspect39.invoke(ProducerAspect39.java) | at org.jboss.jms.client.delegate.ClientProducerDelegate$send_3961598017717988886.invokeNext(ClientProducerDelegate$send_3961598017717988886.java) | at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170) | at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) | at org.jboss.jms.client.delegate.ClientProducerDelegate$send_3961598017717988886.invokeNext(ClientProducerDelegate$send_3961598017717988886.java) | at org.jboss.jms.client.delegate.ClientProducerDelegate.send(ClientProducerDelegate.java) | at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:164) | at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:207) | at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:145) | at org.jboss.jms.client.JBossMessageProducer.send(JBossMessageProducer.java:136) | at org.jboss.jms.server.bridge.Bridge.sendBatch(Bridge.java:1200) | at org.jboss.jms.server.bridge.Bridge.access$1700(Bridge.java:65) | at org.jboss.jms.server.bridge.Bridge$SourceListener.onMessage(Bridge.java:1551) | at com.ibm.mq.jms.MQMessageConsumer.receiveAsync(MQMessageConsumer.java:2969) | at com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java:406) | at java.lang.Thread.run(Thread.java:595) | Had a look at the code and well the error message says it all. WSMQ is putting additional JMSX properties in the message header. What is the reasoning behind not allowing other options. Is it a spec compliance thing? It much easier to make changes to JBM is it possilbe to set some sort of spec compliance flag to allow non-compliant messages to flow through JBM cheers Aaron View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111064#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...