I added additional default hacks to the JBossMessageEndpointFactory, and am back to this exception, although the test runs. Can you look at getting the org.jboss.test.cts.test.MDBUnitTestCase running cleanly Adrian? I can't see where these unspecified values were coming from before the metadata change. There are also numerous errors coming from the jms layer about not finding a session, so it seems the shutdown on undeployment is unclean. | org.jboss.deployment.DeploymentException: Required config property RequiredConfigPropertyMetaData@5fb8424e[name=destination descriptions=[DescriptionMetaData@629609cc[language=en]]] for messagingType 'javax.jms.MessageListener' not found in activation config [] ra=jboss.jca:service=RARDeployment,name='jms-ra.rar' | at org.jboss.resource.deployment.ActivationSpecFactory.createActivationSpec(ActivationSpecFactory.java:95) | at org.jboss.resource.deployers.RARDeployment.createActivationSpec(RARDeployment.java:312) | at org.jboss.resource.deployers.RARDeployment.internalInvoke(RARDeployment.java:276) | at org.jboss.system.ServiceDynamicMBeanSupport.invoke(ServiceDynamicMBeanSupport.java:156) | at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.jboss.ejb.plugins.inflow.JBossMessageEndpointFactory.createActivationSpec(JBossMessageEndpointFactory.java:453) | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096256#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...