I kept running into this so I added a hack to ensure the destination and destinationType properties were in the activation config. I don't see how a legacy 2.0 mdb deployment could have been providing the info needed by the JBossMessageEndpointFactory.augmentActivationConfigProperties(). | // Another hack for pre-ejb 2.1 deployments? | else if(properties.containsKey("destination") == false) | { | String jndiName = metaData.getDestinationJndiName(); | if(jndiName != null) | { | org.jboss.metadata.ejb.spec.ActivationConfigPropertyMetaData acpmd = new | org.jboss.metadata.ejb.spec.ActivationConfigPropertyMetaData(); | acpmd.setActivationConfigPropertyName("destination"); | acpmd.setValue(jndiName); | ActivationConfigPropertyMetaData wrapper = new ActivationConfigPropertyMetaData(acpmd); | properties.put("destination", wrapper); | } | String type = metaData.getDestinationType(); | if(type != null) | { | org.jboss.metadata.ejb.spec.ActivationConfigPropertyMetaData acpmd = new | org.jboss.metadata.ejb.spec.ActivationConfigPropertyMetaData(); | acpmd.setActivationConfigPropertyName("destinationType"); | acpmd.setValue(type); | ActivationConfigPropertyMetaData wrapper = new ActivationConfigPropertyMetaData(acpmd); | properties.put("destinationType", wrapper); | } | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096334#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...