Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-19227

:migrate operation on legacy 6.4.x messaging subsystem fails with 7.4.0.CD19 (WF19)

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Won't Fix
    • Affects Version/s: 7.4.0.CD19
    • Fix Version/s: None
    • Component/s: JMS, Migration
    • Labels:
      None

      Description

      CD19 (WF19) introduces several failures in tests running the :migrate operation on legacy configuration files.

      See standalone-full-ha-migrate.xml.original for configuration file which is subject of migration.

      ...
              <broadcast-groups>
                  <broadcast-group name="groupS">
                      <socket-binding>messaging-group</socket-binding>
                  </broadcast-group>
      ...
              </broadcast-groups>
      ...
      

      See standalone-full-ha-migrate.xml.migrated for configuration file after migration using 7.3.0 EAP.

      ...
              <broadcast-group socket-binding="messaging-group" name="groupS"/>
      ...
      

      Migration outcome with 7.4.0.CD19.CR1 (WF19)

      {
          "outcome" : "failed",
          "result" : {
              "migration-warnings" : [],
              "migration-error" : {
                  "operation" : {
                      "socket-binding" : "messaging-group",
                      "connectors" : null,
                      "operation" : "add",
                      "address" : [
                          {
                              "subsystem" : "messaging-activemq"
                          },
                          {
                              "server" : "default"
                          },
                          {
                              "broadcast-group" : "groupS"
                          }
                      ],
                      "operation-headers" : {
                          "caller-type" : "user",
                          "access-mechanism" : "NATIVE"
                      }
                  },
                  "result" : {
                      "outcome" : "failed",
                      "failure-description" : "WFLYCTL0155: 'connectors' may not be null",
                      "rolled-back" : true
                  }
              }
          },
          "failure-description" : "WFLYMSG0081: Migration failed, see results for more details.",
          "rolled-back" : true
      }
      

      Unfortunately I do not have a deeper knowledge of messaging subsystem to be able to tell what should be the best outcome of migration here.

      Could be related to https://issues.redhat.com/browse/WFLY-10339 Broadcast/discovery-group resources have ambiguous requirement specs

      Steps to reproduce

      $ cp standalone-full-ha-migrate.xml.original jboss-eap-7.4/standalone/configuration/standalone.xml
      $ ./jboss-eap-7.4/bin/jboss-cli.sh 
      You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
      [disconnected /] embed-server --admin-only=true 
      [standalone@embedded /] /subsystem=messaging:migrate
      {
          "outcome" => "failed",
      ...
      

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  ehugonnet Emmanuel Hugonnet
                  Reporter:
                  pkremens Petr Kremensky
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: