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

[GSS](7.4.0) WFLY-14408 - journal-import command fails if in-vm connector has a server-id other than "0"

XMLWordPrintable

    • False
    • False
    • +
    • Undefined
    • Hide

      Configure a JBoss EAP 7 instance with an in-vm connector and acceptor with a server-id other than "0".

      Export messages from the same or other JBoss instance in admin mode.

      Attempt to re-import messages into the current instance runing in normal mode via the cli method.

      Operation fails as described above.

      Show
      Configure a JBoss EAP 7 instance with an in-vm connector and acceptor with a server-id other than "0". Export messages from the same or other JBoss instance in admin mode. Attempt to re-import messages into the current instance runing in normal mode via the cli method. Operation fails as described above.

      If the in-vm-connector / in-vm-acceptor for the default / live messaging-activemq server is configured with a server-id higher than "0":

      <in-vm-connector name="in-vm-connector1" server-id="1"/>

      then performing an import-journal operation from the cli fails with a rather unhelpful "Cannot connect to server(s)" message:

      [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=ServerLive:import-journal(file=/home/jboss/messages.xml) { "outcome" => "failed", "failure-description" => "AMQ219007: Cannot connect to server(s). Tried with all available servers.", "rolled-back" => true }

      After much debugging, resetting the server-id to "0" on the live server in-vm acceptor and connector and from "2" to "1" on the backup resolved the issue and the import succeeded.

        1. journal-20220104-134925278+0100-dump.xml
          0.1 kB

              rchakrab Ranabir Chakraborty
              rchakrab Ranabir Chakraborty
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: