JBoss shutdown is slow

[sergiu_pienar]

Hi,

On a 5.1.0GA. server,at shutdown :

Normally, when I call shutdown on the jboss, I would expect that the following happens:

1.       all MDBs do stop processing any further JMS

2.       all (Quartz) jobs are closing down

3.       jboss is shutting down itself

However, it seems that the MDBs closing is not happening – at least this is not the first task, but the MDBs do still process

messages though jboss did already start to close EJB components (which is actually bad) and thus the total shutdown takes

really a while.There are several exceptions(NameNotFound) raised when lookup is made for objects that have been unbound from the JNDI tree.

Can I force somehow the order in which components are stopped , and stop MDB's first ?

Thx.

[wdfink]

Is the MDB and the EJB component of the same EAR file?

[sergiu_pienar]

Yes.

[wdfink]

Is it EJB3? Do you use @EJB to reference the session bean?

I don't know other way to declare dependency, maybe the deployment descriptor (but not a intuitive one).

IMHO the container should be responsible for this, if there is no way it will be a reason to raise a JIRA bug

[sergiu_pienar]

It's EJB3.

The thing is ... I would be interested in knowing if there's some mechanism that would allow us to specify the order in which components are stopped.

Is there any such mechanism to your knowledge ?

Thank you.

[jaikiran]

If you are looking up a EJB from the MDB, then the container can't implicitly add the dependency. If you however, use a @EJB it will add the necessary dependencies for you.

If you still want to manually do the lookup and still get the dependencies right, then you will have to manually setup the dependencies via the jboss.xml file. Add a <depends> element in the jboss.xml for the MDB pointing to the MBean of the EJB that it depends on.

[sergiu_pienar]

Will try that Jaikiran.

Thank you.

[sergiu_pienar]

Fixed by using mbean's to stop the MDB on server shutdown notification.