how to delay autodeployer until all other services are start

[michel1]

Hi,

I have a problem where my .ear gets deployed by the autodeployer before JmsXA is properly started.

The .ear contains a servlet which is loaded on startup, which publishes a message. Because JmsXA is not yet started, this fails.

Suggestions are welcome.

[adrian.brock]

you don't need the latest code, but in order for you to be able to use hsqldb, you're going to want to do a build against the source.

use this link: http://prdownloads.sourceforge.net/jboss/nukes-1.0.0-src.zip?download

once you've got the source, follow the instruction i posted before. one thing i realize i forgot to mention is that you will need the nukes-ds.xml file deployed in order for the beanshell scripts to work.

you could accomplish this by executing "build deploy" and then manually removing the nukes.ear file from the deploy directory (leaving only the nukes-ds.xml) file.

if this still doesn't work, could you post a step-by-step list of the steps you are taking so i can provide better support?

[michel1]

After some experimenting I found out that making two autodeployers, one which deploys JBoss's RARs and the other which deploys applications, works.

Here is a sample snippet from jboss.jcml:
<!-- ==================================================================== -->
<!-- Auto deployment -->
<!-- ==================================================================== -->


JCA:service=RARDeployer

../deploy/lib




J2EE:service=J2eeDeployer;

../deploy



AutoDeployer deploys the JBoss RARs which are found in the /deploy/lib dir.
AutoDeployer2 deploys applications and can point anywhere (here it is the default /deploy dir).

[marc.fleury]

clever :)

[michel1]

Can you tell me what this does?

[adrian.brock]

This attribute stops the second AutoDeployer
running when it is first started. Instead it will wait 30 secs before trying to deploy anything.

Thinking about it, a better approach in future versions is to make the J2eeDeployer depend upon the JMS services using <mbean-ref> in its service.xml

[davidjencks]

You might be able to do the same thing with one Autodeployer by judiciously rearranging the order of the deployment directories (and maybe adding more) and the order of the deployers.