Not able to do exploded deployment using rollout-plan in domain mode

[Deepak Yadav]

Hi All,

In my environment, we have setup a server group in domain mode. Server group consists of 2 nodes, each node having 2 servers.

I am trying to deploy exploded application using rollout-plan so that there is no downtime for the application.

Rollout-plan is working fine with option --headers={rollout server-group(rolling-to-servers=true)} --force

But I need exploded version of the application so that I can patch files easily later on through console.

Any thoughts on how to achieve this?

[Brian Stansberry]

Are you talking about a managed exploded deployment, as discussed at https://docs.wildfly.org/24/Admin_Guide.html#exploded-managed-deployments ?

Or is it unmanaged, as discussed at https://docs.wildfly.org/24/Admin_Guide.html#unmanaged-deployments ?

If the latter, please note that you must ensure that a copy of the content is present on all machines that have servers in the target server groups, all at the same filesystem path. The domain will not copy the files for you.

Best regards,

Brian

[Deepak Yadav]

Hi Brian,

It's a managed exploded deployment but I want to deploy the app using rollout-plan so that there is no downtime on my production.

I am able to do that with downtime following steps like stopping servers, undeploying app, deploying new version, exploding app and then starting servers.

But with rollout-plan, it is deploying app one by one on all servers in server-group and since app is already deployed and running, I am not able to explode it.

Thanks

Deepak

[Brian Stansberry]

Can you post the commands you are trying?

[Deepak Yadav]

Command to deploy app using rollout-plan:

deploy "/path_to_ear/test.ear" --name=Test_App --runtime-name=test.ear --headers={rollout main-server-group(rolling-to-servers=true)} --force

Command to exlpode app:

./jboss-cli.sh --connect /deployment=Test_App:explode

Following is the error after executing the explode command:

{

  "outcome" => "failed",

  "result" => undefined,

  "failure-description" => {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {" main-server-group " => {"host" => {"node1" => {"server1" => "WFLYSRV0245: Cannot explode an already deployed deployment"}}}}}},

  "rolled-back" => true,

  "server-groups" => {" main-server-group " => {"host" => {"node1" => {"server1" => {"response" => {

  "outcome" => "failed",

  "result" => undefined,

  "failure-description" => "WFLYSRV0245: Cannot explode an already deployed deployment",

  "rolled-back" => true

  }}}}}}

}

[Emmanuel Hugonnet]

You can only explode a deployment that is not running / enabled.
Emmanuel

> --
> You received this message because you are subscribed to the Google Groups "WildFly" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/wildfly/76a42d51-3560-4591-917d-4ad1bdd5a153n%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/76a42d51-3560-4591-917d-4ad1bdd5a153n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Brian Stansberry]

Adding content to https://docs.wildfly.org/24/Admin_Guide.html#managed-domain-3 to walk through this use case would be good.