anonymous wrote : why does the ESB aware need to handle property mappings? This is to support pass-through of JMS properties. Previously we just passed through all properties which caused problems with some JMS Providers. The issue we had was when working with IBMQ in combination with JBossMQ. JBossMQ throws an exception if a provider specific jms property, one starting with "JMS_verndor_name" was not recognized as it's own. JBoss Messaging would simply ignore an unrecognized provider property. The use case was a jms gateway that was connected to IBMQ. A JMS Message would in this case contain provider specific properties to IBMQ. By filtering out these properties they would never be seen by JBossMQ. We created this for cases where other JMS Providers might do the same as JBossMQ and added the ability to filter out properties. anonymous wrote : should the DefaultJmsPropertiesSetter also be filtering? Yeah, it probably should. If there is a mix of JMS Provders this will probably cause troubles like the one you are seeing at the moment :( anonymous wrote : should we be ignoring JMS_XXX on a global basis? Well this might make our life easier but perhaps this could hurt performance. These properties could be optimization properties that the provider can take advantage of. /Daniel View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230846#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...