I had correctly set up the queue correctly using the JNDIName attribute - and after starting JBoss the queue showed up in the Administration console as expected.... so I'm confident my queue was set up correctly.
The link below indicates that this (MDB deployer not "seeing" the destination queue) is a recognized bug in JBoss when using EJB3: http://jira.jboss.org/jira/browse/EJBTHREE-541?page=all Not sure if this means that I'm encountering the same root problem as was encountered for that bug report (since I'm not using annotations). I will grant you, though, that it is strange that the MDB sample worked correctly, not creating a special Queue/JNDI name for its MDB.... perhaps the problem is that the JNDI name I specified starts with jms instead of queue (i.e. jms/OrderQueue instead of queue/OrderQueue)?? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4149479#4149479 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4149479 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
