-
Bug
-
Resolution: Done
-
Major
-
7.1.0.DR5, 7.1.0.DR6, 7.1.0.DR7
-
None
Deploying an empty exploded deployment created on domain controller fails with the following:
[domain@localhost:9990 /] /deployment=empty-deployment.jar:add(content=[{empty=true}]) { "outcome" => "success", "result" => undefined, "server-groups" => undefined } [domain@localhost:9990 /] /server-group=main-server-group/deployment=empty-deployment.jar:add() { "outcome" => "failed", "result" => undefined, "failure-description" => {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"main-server-group" => {"host" => {"master" => { "server-one" => "WFLYSRV0201: Cannot have more than one of [bytes, input-stream-index, hash, url, empty]", "server-two" => "WFLYSRV0201: Cannot have more than one of [bytes, input-stream-index, hash, url, empty]" }}}}}}, "rolled-back" => true, "server-groups" => {"main-server-group" => {"host" => {"master" => { "server-one" => {"response" => { "outcome" => "failed", "failure-description" => "WFLYSRV0201: Cannot have more than one of [bytes, input-stream-index, hash, url, empty]", "rolled-back" => true }}, "server-two" => {"response" => { "outcome" => "failed", "failure-description" => "WFLYSRV0201: Cannot have more than one of [bytes, input-stream-index, hash, url, empty]", "rolled-back" => true }} }}}} }
- is cloned by
-
WFCORE-1959 Deploying an empty managed exploded deployment to server group in domain fails
- Resolved
- is incorporated by
-
JBEAP-6556 (7.1.0) Upgrade to WildFly Core 3.0.0.Alpha12
- Closed