Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-754

EAP fails to start with -bmanagement= option and with specific IP settings

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 1.0.0.CR7, 2.0.0.Alpha5
    • 1.0.0.CR5, 2.0.0.Alpha1
    • Management
    • None

      Description of problem:

      • EAP fails to start with -bmanagement= option. IPv4 address is used in this option.
      • Host Controller starts to listening on IPv4:9999
      • Server:server-one probably resolve IPv4 address to host name. Server-one tries to connect to this host name. Hostname is resolved by ping ($ ping dev98) to IPv6 address, where host controller is not listening.
      • This error doesn't occur, if hostname is resolved to IPv4 address by ping on machine.
      • This error doesn't occur on EAP 6.4.0

      How reproducible:

      • windows

      Steps to Reproduce:
      Example on dev98 machine:

      1. ssh dev98
      2. ping dev98
        Pinging dev98 [fe80::699a:d857:e5cc:e3b7%14] with 32 bytes of data:
        Reply from fe80::699a:d857:e5cc:e3b7%14: time<1ms 
        Reply from fe80::699a:d857:e5cc:e3b7%14: time<1ms 
        Reply from fe80::699a:d857:e5cc:e3b7%14: time<1ms 
        Reply from fe80::699a:d857:e5cc:e3b7%14: time<1ms 
        
        Ping statistics for fe80::699a:d857:e5cc:e3b7%14:
            Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
        Approximate round trip times in milli-seconds:
            Minimum = 0ms, Maximum = 0ms, Average = 0ms
        
      3. ping -a 10.16.92.7
        Pinging dev98 [10.16.92.7] with 32 bytes of data:
        Reply from 10.16.92.7: bytes=32 time<1ms TTL=128
        Reply from 10.16.92.7: bytes=32 time<1ms TTL=128
        Reply from 10.16.92.7: bytes=32 time<1ms TTL=128
        Reply from 10.16.92.7: bytes=32 time<1ms TTL=128
        
        Ping statistics for 10.16.92.7:
            Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
        Approximate round trip times in milli-seconds:
            Minimum = 0ms, Maximum = 0ms, Average = 0ms
        
      4. domain.bat -bmanagement=10.16.92.7

      Actual results:

      .....
      [Host Controller] 06:49:07,673 INFO  [org.jboss.as.remoting] (MSC service thread 1-3) WFLYRMT0001: Listening on 10.16.92.7:9999
      .....
      [Server:server-one] 06:49:16,251 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 2) MSC000001: Failed to start service jboss.server-boot-operations: org.jboss.msc.service.StartException in service jboss.server-boot-operations: java.net.ConnectException: WFLYPRT0053: Could not connect to remote://dev98:9999. The connection failed
      [Server:server-one] 	at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:72)
      [Server:server-one] 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
      [Server:server-one] 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
      [Server:server-one] 	at java.lang.Thread.run(Thread.java:745)
      [Server:server-one] 	at org.jboss.threads.JBossThread.run(JBossThread.java:320)
      [Server:server-one] Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote://dev98:9999. The connection failed
      [Server:server-one] 	at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:122)
      [Server:server-one] 	at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:257)
      [Server:server-one] 	at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:71)
      [Server:server-one] 	at org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:130)
      [Server:server-one] 	at org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:85)
      [Server:server-one] 	at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:68)
      [Server:server-one] 	... 4 more
      

      Expected results:
      No errors

              ehugonne1@redhat.com Emmanuel Hugonnet
              mkopecky@redhat.com Marek Kopecky
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: