Uploaded image for project: 'JBoss Server Migration Tool'
  1. JBoss Server Migration Tool
  2. CMTOOL-346

HA configurations fails after two-step migration from EAP 6.4

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Major Major
    • None
    • 1.12.0.Final
    • EAP 8.0
    • None
    • False
    • None
    • False

      When performing two-step migration from EAP 6.4/6.4.23 to EAP 8 test build through EAP 7.4.11, server with a kitchensink QS deployment cannot be started with standalone-ha.xml configuration:

      ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 28) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.ee-ejb: org.jboss.msc.service.StartException in service org.wildfly.clustering.jgroups.channel.ee-ejb: java.lang.IllegalStateException: java.lang.IllegalArgumentException: failed to start server socket
      	at org.wildfly.clustering.service@8.0.0.GA-redhat-20230605//org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:66)
      	at org.wildfly.clustering.service@8.0.0.GA-redhat-20230605//org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$start$0(AsyncServiceConfigurator.java:117)
      	at org.jboss.threads@2.4.0.Final-redhat-00001//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
      	at org.jboss.threads@2.4.0.Final-redhat-00001//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
      	at org.jboss.threads@2.4.0.Final-redhat-00001//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
      	at org.jboss.threads@2.4.0.Final-redhat-00001//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
      	at java.base/java.lang.Thread.run(Thread.java:829)
      	at org.jboss.threads@2.4.0.Final-redhat-00001//org.jboss.threads.JBossThread.run(JBossThread.java:513)
      Caused by: java.lang.IllegalStateException: java.lang.IllegalArgumentException: failed to start server socket
      	at org.jboss.as.clustering.jgroups@8.0.0.GA-redhat-20230605//org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:122)
      	at org.jboss.as.clustering.jgroups@8.0.0.GA-redhat-20230605//org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:60)
      	at org.wildfly.clustering.service@8.0.0.GA-redhat-20230605//org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:63)
      	... 7 more
      Caused by: java.lang.IllegalArgumentException: failed to start server socket
      	at org.jgroups@5.2.14.Final-redhat-00001//org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:379)
      	at org.jgroups@5.2.14.Final-redhat-00001//org.jgroups.protocols.FailureDetection.down(FailureDetection.java:159)
      	at org.jgroups@5.2.14.Final-redhat-00001//org.jgroups.protocols.VERIFY_SUSPECT.down(VERIFY_SUSPECT.java:102)
      	at org.jgroups@5.2.14.Final-redhat-00001//org.jgroups.protocols.pbcast.NAKACK2.down(NAKACK2.java:640)
      	at org.jgroups@5.2.14.Final-redhat-00001//org.jgroups.protocols.UNICAST3.down(UNICAST3.java:639)
      	at org.jgroups@5.2.14.Final-redhat-00001//org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:276)
      	at org.jgroups@5.2.14.Final-redhat-00001//org.jgroups.protocols.pbcast.GMS.down(GMS.java:890)
      	at org.jgroups@5.2.14.Final-redhat-00001//org.jgroups.protocols.FlowControl.down(FlowControl.java:201)
      	at org.jgroups@5.2.14.Final-redhat-00001//org.jgroups.protocols.FlowControl.down(FlowControl.java:201)
      	at org.jgroups@5.2.14.Final-redhat-00001//org.jgroups.stack.Protocol.down(Protocol.java:283)
      	at org.jgroups@5.2.14.Final-redhat-00001//org.jgroups.protocols.FRAG3.down(FRAG3.java:98)
      	at org.jgroups@5.2.14.Final-redhat-00001//org.jgroups.stack.Protocol.down(Protocol.java:283)
      	at org.jgroups@5.2.14.Final-redhat-00001//org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:929)
      	at org.jgroups@5.2.14.Final-redhat-00001//org.jgroups.JChannel.down(JChannel.java:608)
      	at org.jgroups@5.2.14.Final-redhat-00001//org.jgroups.JChannel._connect(JChannel.java:808)
      	at org.jgroups@5.2.14.Final-redhat-00001//org.jgroups.JChannel.connect(JChannel.java:325)
      	at org.jgroups@5.2.14.Final-redhat-00001//org.jgroups.JChannel.connect(JChannel.java:316)
      	at org.jboss.as.clustering.jgroups@8.0.0.GA-redhat-20230605//org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:117)
      	... 9 more
      Caused by: java.net.BindException: No available port to bind to in range [54200 .. 54200]
      	at org.jgroups@5.2.14.Final-redhat-00001//org.jgroups.util.Util.bind(Util.java:4049)
      	at org.jgroups@5.2.14.Final-redhat-00001//org.jgroups.util.Util.createServerSocket(Util.java:4025)
      	at org.jgroups@5.2.14.Final-redhat-00001//org.jgroups.protocols.FD_SOCK.startServerSocket(FD_SOCK.java:640)
      	at org.jgroups@5.2.14.Final-redhat-00001//org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:376)
      	... 26 more
      

              emartins@redhat.com Eduardo Martins
              okotek@redhat.com Ondrej Kotek
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: