[jboss-jira] [JBoss JIRA] (WFCORE-549) Issue with adding server-group and server-config in one composite operation
Brian Stansberry (JIRA)
issues at jboss.org
Wed Apr 27 11:31:01 EDT 2016
[ https://issues.jboss.org/browse/WFCORE-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Stansberry resolved WFCORE-549.
-------------------------------------
Resolution: Out of Date
Thanks, Martin.
> Issue with adding server-group and server-config in one composite operation
> ---------------------------------------------------------------------------
>
> Key: WFCORE-549
> URL: https://issues.jboss.org/browse/WFCORE-549
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Environment: JBoss EAP 6.1.0 GA
> DC and two HC
> Reporter: Oleg Koropita
>
> I used such request to add two server-groups and four servers
> {
> "operation" => "composite",
> "address" => [],
> "steps" => [
> {
> "operation" => "add",
> "socket-binding-port-offset" => 0,
> "status" => "STOPPED",
> "auto-start" => false,
> "group" => "primary-server-group",
> "socket-binding-group" => "standard-sockets",
> "address" => [
> ("host" => "node02"),
> ("server-config" => "system2-server1")
> ]
> },
> {
> "operation" => "stop",
> "name" => "server",
> "value" => "system2-server1",
> "address" => [
> ("host" => "node02"),
> ("server-config" => "system2-server1")
> ]
> },
> {
> "operation" => "add",
> "socket-binding-port-offset" => 150,
> "status" => "STOPPED",
> "auto-start" => false,
> "group" => "secondary-server-group",
> "socket-binding-group" => "standard-sockets",
> "address" => [
> ("host" => "node02"),
> ("server-config" => "system2-server2")
> ]
> },
> {
> "operation" => "stop",
> "name" => "server",
> "value" => "system2-server2",
> "address" => [
> ("host" => "node02"),
> ("server-config" => "system2-server2")
> ]
> },
> {
> "operation" => "add",
> "socket-binding-port-offset" => 0,
> "status" => "STOPPED",
> "auto-start" => false,
> "group" => "primary-server-group",
> "socket-binding-group" => "standard-sockets",
> "address" => [
> ("host" => "node01"),
> ("server-config" => "system1-server1")
> ]
> },
> {
> "operation" => "stop",
> "name" => "server",
> "value" => "system1-server1",
> "address" => [
> ("host" => "node01"),
> ("server-config" => "system1-server1")
> ]
> },
> {
> "operation" => "add",
> "socket-binding-port-offset" => 150,
> "status" => "STOPPED",
> "auto-start" => false,
> "group" => "secondary-server-group",
> "socket-binding-group" => "standard-sockets",
> "address" => [
> ("host" => "node01"),
> ("server-config" => "system1-server2")
> ]
> },
> {
> "operation" => "stop",
> "name" => "server",
> "value" => "system1-server2",
> "address" => [
> ("host" => "node01"),
> ("server-config" => "system1-server2")
> ]
> },
> {
> "operation" => "add",
> "socket-binding-group" => "standard-sockets",
> "profile" => "default",
> "address" => [("server-group" => "primary-server-group")]
> },
> {
> "operation" => "add",
> "socket-binding-group" => "standard-sockets",
> "profile" => "default",
> "address" => [("server-group" => "secondary-server-group")]
> }
> ]
> }
> And I received such result:
> {
> "outcome" => "success",
> "result" => {
> "step-1" => {"outcome" => "success"},
> "step-2" => {
> "outcome" => "success",
> "result" => "STOPPED"
> },
> "step-3" => {"outcome" => "success"},
> "step-4" => {
> "outcome" => "success",
> "result" => "STOPPED"
> },
> "step-5" => {"outcome" => "success"},
> "step-6" => {
> "outcome" => "success",
> "result" => "STOPPED"
> },
> "step-7" => {"outcome" => "success"},
> "step-8" => {
> "outcome" => "success",
> "result" => "STOPPED"
> },
> "step-9" => undefined,
> "step-10" => undefined
> },
> "server-groups" => undefined
> }
> But, when I checked admin console, there were no server-groups.
> The same with domain.xml on DC side.
> So server-groups wasn't addedd.
> But if I try to add server-groups one more time:
> {
> "operation" => "composite",
> "address" => [],
> "steps" => [
> {
> "operation" => "add",
> "socket-binding-group" => "standard-sockets",
> "profile" => "default",
> "address" => [("server-group" => "primary-server-group")]
> },
> {
> "operation" => "add",
> "socket-binding-group" => "standard-sockets",
> "profile" => "default",
> "address" => [("server-group" => "secondary-server-group")]
> }
> ]
> }
> I will get such result:
> {
> "outcome" => "failed",
> "result" => {
> "step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> },
> "step-2" => {
> "outcome" => "failed",
> "rolled-back" => true
> }
> },
> "failure-description" => {"host-failure-descriptions" => {
> "node02" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014803: Duplicate resource [(\"server-group\" => \"primary-server-group\")]"}},
> "node01" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014803: Duplicate resource [(\"server-group\" => \"primary-server-group\")]"}}
> }},
> "rolled-back" => true
> }
> Then I need to restart DC to restore server. And after that, I can successuflly add server-groups.
> So, after first request, JBoss AS stuck on some uncommited state.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list