I face a similar problem. Sometimes, there are still messages in a queue when JBoss is shutdown intentionally for maintenance. During the next startup of JBoss, before all the EJBs are successfully deployed, the previously-queued messages have already started to be processed by the MDBs. As the processing of those queued messages requires the EJBs that are still being deployed, there are lots of NameNotFound exceptions and transaction rollbacks during JBoss startup.

Can JBoss be configured to start delivering queued messages to MDBs only after the complete startup of JBoss? This capability will help a lot by removing the tons of exceptions that are not supposed to happen.

By the way, I am using jboss-4.0.4.GA-Patch1.

Thanks.

Hann Wei

You can add to your MDB so they don't start too soon. Check out the DTD.

"genman" wrote:

You can add <depends> to your MDB so they don't start too soon. Check out the DTD.

 <invoker-proxy-binding>
 <name>message-driven-bean</name>
 <invoker-mbean>default</invoker-mbean>
 <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
 <proxy-factory-config>
 <JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI>
 <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
 <CreateJBossMQDestination>true</CreateJBossMQDestination>
 <!-- WARN: Don't set this to zero until a bug in the pooled executor is fixed -->
 <MinimumSize>1</MinimumSize>
 <MaximumSize>15</MaximumSize>
 <KeepAliveMillis>30000</KeepAliveMillis>
 <MaxMessages>1</MaxMessages>
 <MDBConfig>
 <ReconnectIntervalSec>10</ReconnectIntervalSec>
 <DeliveryActive>false</DeliveryActive>
 <DLQConfig>
 <DestinationQueue>queue/DLQ</DestinationQueue>
 <MaxTimesRedelivered>10</MaxTimesRedelivered>
 <TimeToLive>0</TimeToLive>
 </DLQConfig>
 </MDBConfig>
 </proxy-factory-config>
 </invoker-proxy-binding>

 <invoker-proxy-binding>
 <name>singleton-message-driven-bean</name>
 <invoker-mbean>default</invoker-mbean>
 <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
 <proxy-factory-config>
 <JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI>
 <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
 <CreateJBossMQDestination>true</CreateJBossMQDestination>
 <!-- WARN: Don't set this to zero until a bug in the pooled executor is fixed -->
 <MinimumSize>1</MinimumSize>
 <MaximumSize>1</MaximumSize>
 <KeepAliveMillis>30000</KeepAliveMillis>
 <MaxMessages>1</MaxMessages>
 <MDBConfig>
 <ReconnectIntervalSec>10</ReconnectIntervalSec>
 <DeliveryActive>false</DeliveryActive>
 <DLQConfig>
 <DestinationQueue>queue/DLQ</DestinationQueue>
 <MaxTimesRedelivered>10</MaxTimesRedelivered>
 <TimeToLive>0</TimeToLive>
 </DLQConfig>
 </MDBConfig>
 </proxy-factory-config>
 </invoker-proxy-binding>

There should be a startDelivery and stopDelivery method someplace: http://docs.jboss.org/jbossas/getting_started/v4/html/mdb.html

"genman" wrote:
There should be a startDelivery and stopDelivery method someplace: http://docs.jboss.org/jbossas/getting_started/v4/html/mdb.html

jboss.j2ee
 - ear=aps.ear,jar=aps-ejb.jar,name=LocalReplyMDB,service=EJB3

...
MBean Java Class: org.jboss.ejb3.ServiceDelegateWrapper
...

List of MBean operations:
void start()
void create()
void jbossInternalLifecycle()
void stop()
void destroy()

@MessageDriven
 (activationConfig=
 {
 @ActivationConfigProperty(propertyName="destinationType",
 propertyValue="javax.jms.Queue"),
 @ActivationConfigProperty(propertyName="destination",
 propertyValue="queue/aps/localReply")
 }
 )
public class LocalReplyMDB
 implements MessageListener
{

http://jira.jboss.com/jira/browse/EJBTHREE-372

EJB3 issue I guess.

Correct. These are features that are being carried over to the JMS/JCA adapter which is the default messaging provider for EJB3 after RC9.