Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-16013

Discovery Group can't change from Socket binding to Jgroups cluster.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 29.0.0.Final
    • None
    • JMS
    • None
    • Hide

      Create 

      /subsystem=messaging-activemq/discovery-group=test:add(socket-binding=test)

      Run batch

      batch
/subsystem=messaging-activemq/discovery-group=test:undefine-attribute(name=socket-binding)
/subsystem=messaging-activemq/discovery-group=test:write-attribute(name=jgroups-cluster, value=testValue)
run-batch 

      and following error appear

      WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:
Step: step-1
Operation: /subsystem=messaging-activemq/discovery-group=test:undefine-attribute(name=socket-binding)
Failure: WFLYCTL0155: 'socket-binding' may not be null
      Show
      Create  /subsystem=messaging-activemq/discovery-group=test:add(socket-binding=test) Run batch batch /subsystem=messaging-activemq/discovery-group=test:undefine-attribute(name=socket-binding) /subsystem=messaging-activemq/discovery-group=test:write-attribute(name=jgroups-cluster, value=testValue) run-batch  and following error appear WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed: Step: step-1 Operation: /subsystem=messaging-activemq/discovery-group=test:undefine-attribute(name=socket-binding) Failure: WFLYCTL0155: 'socket-binding' may not be null

      When creating discovery group with Jgroups cluster attribute it isn't possible to change to socket binding attribute. The same outcome is when discovery group is created with socket binding and trying set Jgroup.  Issue is located on adress 

      /subsystem=messaging-activemq/discovery-group

       and 

      /subsystem=messaging-activemq/server=default/discovery-group

       

       

              thofman Tomas Hofman
              thofman Tomas Hofman
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: