We have an issues the is hanging the server during some operation that sends a bunch of messages. We're trying to id that issue.
As a result, we have several messages added to the queue that don't get comsumed by our MDB.
Here is my concern, when we restart the server the messages are consumed by the MDB BEFORE the SessionBean the MDB communicates with has been deployed. Therefore, all the messages are consumed and an error message is displayed for each message about not finding a resource (the session bean).
How can I prevent these messages from getting consumed until the entire application has been deployed?
Are you seeing the same problem as I am? Does your MDB process messages during normal operation of your server?
To solve your problem, can you put your MDB and Session beans in the same EAR file? Then they would both be deployed simultaneously?
Please check my message to see if you are having the same problem: http://jboss.org/forums/thread.jsp?forum=48&thread=14502