Uploaded image for project: 'Application Server 7'
  1. Application Server 7
  2. AS7-5409

CLONE - Unable to disable -Djava.net.preferIPv4=true in domain mode without editing domain.conf

    Details

    • Affects:
      Release Notes
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      Workaround for this is to change the argument in domain.conf to -Djava.net.preferIPv4Stack=false (or remove it); after that, the process will know that it is supposed to use IPv6.

      Show
      Workaround for this is to change the argument in domain.conf to -Djava.net.preferIPv4Stack=false (or remove it); after that, the process will know that it is supposed to use IPv6.

      Description

      Try running EAP domain mode like this:

      bin/domain.sh -Djava.net.preferIPv4Stack=false -bmanagement=::1
      

      It will fail:

      [Host Controller] 09:40:49,647 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.network.management: org.jboss.msc.service.StartException in service jboss.network.management: JBAS015810: failed to resolve interface management
      [Host Controller] 	at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:97) [jboss-as-server-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1]
      [Host Controller] 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
      [Host Controller] 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
      [Host Controller] 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
      [Host Controller] 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
      [Host Controller] 	at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
      

      Other interfaces work and can be bound to ipv6, just 'management' does not. (In standalone mode, this issue is not present.)

      Blocks testing of Admin console,Native+HTTP interfaces in domain mode in IPv6, not marking as blocker because workaround exists.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  brian.stansberry Brian Stansberry
                  Reporter:
                  jmartisk Jan Martiska
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: