message-driven-bean

Given: A JMS message queue. A timer service which puts messages to that queue periodically (from a database). A JEE6 message-driven bean which reads from the queue. The timer service and the message-driven bean are part of different deployment units. Problem: The message-driven bean cannot be undeployed, without breaking the workflow state, as long as messages are work in process. Because of that, we stop the timer service first and wait until all messages are finished. Is there a way to automate that behavior? Or is it possible to prevent undeployment if the timer service is still running? We

I'm using EJB 3.1 and I want to configure an MDB to listen to multiple queues. I'd prefer defining the queue names via XML but the other definitions via annotations. Can this be done? Once instantiated, an MDB can only listen to the resource specified in their destination ActivationConfigProperty, however you can create multiple instances of the same MDB with different destinations (queues, in your case). Create two entries in your ejb-jar.xml with different destination and ejb-name properties, but the same ejb-class. use ejb-jar.xml instead of ibm-ejb-jar-bnd.xml <message-driven> <ejb-name