[jboss-user] [Clustering/JBoss] - Re: Farm hot-deploy waits for MDBs to finish?

[bstansberry@jboss.com]

On your first question re: MDBs, you might have better luck on the EJB or JMS forums, as your question is really about the general lifecycle of MDBs; farm service just inherits the basic behavior. There may be a switch or something to get the MDB to abort early (although I doubt it.).

On your second question, I think you're on the right track.  If your MDB and the WAR are packaged in an EAR, then I think just declaring the MDB jar after the WAR in application.xml should result in the MDB deploying last / undeploying first.

If the MDB and WAR are packaged separately, you can add a "depends" element to the MDB's jboss.xml telling it to depend on the WAR's mbean.  There's also tricks you can do with deployment order by how you name packages.  That kind of stuff is covered in the docs.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105267#4105267

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105267