Java – the order of deployment in Wildfly

javajbosswildfly8

I have a large number of services, and a core set of services that are expected to load first so that they are available when the other services load.

Does Wildfly have a specific order (e.g. alphabetical, based on filename) that it uses when doing deployments? Or is there a way to set this up?

We've tried adding code to retry connections if the other services aren't ready yet, but that involved threads, and sometimes the threads didn't get terminated properly when stuff was undeployed.

Some things that don't work for me:

It is possible to control the order of deployment of modules (ejb's, war's, etc…) inside of an .ear, but I'm interested in controling the order of .ear deployments.
An .ear can be set as a dependency of another .ear, but our services are deployed in a variety of regions. We have serviceA-regionA-1.0.0.ear, serviceA-regionB-1.0.0.ear, etc… It would be a big pain to have to specify all of those ear names.

Best Answer

Wildfly (Since AS7) tries to do parallel deployments to speed up the process, if you want do sequential deployment then you can provide dependencies of each deployment on another (like links you have provided in the question).

Alternatively you can use the Management CLI to order your deployment schedule, using the Batch features to ensure that your deployments occur in the order scripted, and If at least one of the commands or operations fails, all the other successfully executed commands and operations in the batch are rolled back.

Related Solutions

How to create a domain global deployable module? (Jboss, Wildfly)

You can use patch feature, this allow apply updates in the servers installations from domain controller. Also you can view patch history and verify patch.

Eg (cli command).

patch --host=server.local apply /<path_to_patch>/patch.zip

You can see a full example in: Patch User Defined WildFly Modules in Domain Mode

Java – How to run Wildfly best

Leaving the deployment scanner on is a security risk.

Set scan-enabled="false" like so:

 <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">
     <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-enabled="false"/>
 </subsystem>

How you start and stop JBoss is really up to you and how you like to manage your server. There are more important things to consider when running JBoss or WildFly in production. This blog post goes over some stuff for JBoss 5. Some things have changed since then, but there is some still relevant stuff there.

One thing I notice is that you are serving requests over port 8080, directly from WildFly. There is a blog post here about securing JBoss EAP 6 , which will still apply to WildFly. The preferred way to do this, however, would be to front your server with a web server or load balancer (Apache or Nginx would do) and completely lock down your WildFly host from any external requests apart from those coming from Apache.

This is a huge topic, to be quite honest, so you will need to spend a lot of time analysing risk and making sure you understand things before potentially leaving security holes in production.

Best Answer

Related Solutions

How to create a domain global deployable module? (Jboss, Wildfly)

Java – How to run Wildfly best

Related Topic