command-line-interfacewildflyjboss-cli

JBoss Cli stop a deployment until next startup

With WildFly 15.0.1 I want to use jboss-cli to stop a deployment, but leave it ready for deployment with the next startup of WildFly.

So far I managed to disable or undeploy it keeping its content (same as disable). But when restarting WildFly, the deployment will continue disabled.

deployment enable name
undeploy name --keep-content

I tried also creating a file name.dodeploy in the deployments folder, but this doesn't work as the deployment was done using the Admin Console.

I know that after restart I could call the enable command, but because of some library link problem we would need that the deployment is started on startup and not triggered later.

Is this possible?

Solution

  • At the end we didn't find a way to solve this issue using console deployments and jboss-cli. Our final approach is using the /deployments folder:

    1. Deploy artifacts by placing them in the /deployments folder
    2. To stop one single deployment, use JBoss CLI to 'disable' that deployment
    3. Then, Shutdown WildFly
    4. Before starting up WildFly, copy a file deployment-name.dodeploy to the /deployments folder
    5. Start WildFly and the deployment will be performed normally on startup