Quick check of moving over to the JCA/JMS adapter. Change in standardjboss.xml is required. The easiest thing is simply to switch the default container configuration from | | <container-name>Standard Message Driven Bean</container-name> | <call-logging>false</call-logging> | <invoker-proxy-binding-name>message-driven-bean</invoker-proxy-binding-name> | to | <container-name>Standard Message Driven Bean</container-name> | <call-logging>false</call-logging> | <invoker-proxy-binding-name>jms-message-inflow-driven-bean</invoker-proxy-binding-name> | Also, as we all know, the old JMSContainerInvoker allowed for creating destinations when a listener was being deployed without one. EJB3 carries this tradition over for EJB3, but for EJB 2.x the JMS/JCA adapter will not. There are a few reasons for this a) It's not portable and JBoss specific b) While we could create a temporary destination using the JMS API, I don't think it is a good idea to carry this 'convenience' forward as it simply masks underlying configuration issues on the client. In sum, you want to use JMS/JCA inflow, create your destination. Further, I am not sure how much from the JMS API without having to fall back on JBoss specific constructs to create the destination. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008640#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...