we are using octopus deploy to deploy a simple helloworld WAR file, using the octopus step ""Deploy to WildFly or Red Hat JBoss EAP" - see Java Applications - Octopus Deploy to a Domain Server. Our Management host is configured to deploy to a different machine to the machine the Octopus package gets pushed to (which is possible). It is configured to use "Remoting" for the management protocol. The deployment is successful - the application is deployed successfully and we can verify that the helloworld page works. However on reboot or restarting the jboss service, the page becomes unresponsive - I get a 403 just like if the WAR file was not deployed.
(1) Jboss reports that the war file is deployed and enabled using the deployment-info command of the jboss-cli.
(2) In the logs of the octopus deploy, it is using the command (this is on the deployment box connected to the target box via remoting)
deploy --force --name=helloworld.war "C:\Octopus\Applications\D51\jboss-helloworld-rs\1.0.1_1\jboss-helloworld-rs.1.0.1.war"
(3) When we restart jboss we get the warning/error:
Can't find helloworld.war under deployments directory!
Can anyone help? There are other files there (ear files) that are deployed on reboot, so it seems particular to this WAR file deployment.
You should be running it like below.
/opt/wildfly/bin/jboss-cli.sh -c --controller=localhost:9990 --command="deploy /opt/wildfly/standalone/deployments/helloworld.war"
or with --force
/opt/wildfly/bin/jboss-cli.sh -c --force --controller=localhost:9990 --command="deploy /opt/wildfly/standalone/deployments/helloworld.war"