-
1. Re: Disable hot deployment in domain mode [9.0.2 final]
ptyagi_redhat.com Jun 8, 2017 5:00 AM (in response to bluething)In domain mode, deployment scanner subsystem is not defined and disabled by default.
- Priyanka
-
2. Re: Disable hot deployment in domain mode [9.0.2 final]
bluething Jun 8, 2017 5:32 AM (in response to ptyagi_redhat.com)Thanks for the answer. So is there any way to do cold deployment in domain mode?
Or it's impossible to do cold deployment with domain mode?
-
3. Re: Disable hot deployment in domain mode [9.0.2 final]
ctomc Jun 8, 2017 6:00 AM (in response to bluething)what do you mean by "cold" deployment.
in domain you can deploy stuff by either CLI command deploy ...
or via admin console
-
4. Re: Disable hot deployment in domain mode [9.0.2 final]
ptyagi_redhat.com Jun 8, 2017 6:10 AM (in response to ctomc)You may refer link application deployment Application deployment - WildFly 9 - Project Documentation Editor
- Priyanka
-
5. Re: Disable hot deployment in domain mode [9.0.2 final]
bluething Jun 9, 2017 12:07 AM (in response to ctomc)"Cold deployment are defined as tasks that require one or more instances of the server to restart to reflect the changes." Hot vs Cold Deployment
I have some problem with current domain mode. During deployment process, sometimes request will failed because the service is not ready yet.I want to control the deployment, upload the artifact to Wildfly (via Jenkins) then leave it to infra guys doing the rest (remove from load balancer, restart the server, add to load balancer) to reflect the changes.