Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-12282

Local AS7/EAP6 fails to stop when bound to IPv6 address or anything but localhost really

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 4.2.3.Beta1, 4.3.0.Alpha1
    • 3.3.0.Final
    • server
    • None
    • Hide

      1. Set up EAP6/AS7 in JBT/JBDS
      2. Open the server in server editor (double-click the server in Server view) and change the Host name to your IPv6 address (i.e. ::1 for localhost)
      3. In the server editor, click Open launch configuration
      4. Uncheck "Always update arguments..."
      5. Add this to program arguments field:
      -b=::1 -bunsecure=::1 -Djboss.default.multicast.address=ff01::1
      6. In the VM arguments field, replace "-Djava.net.preferIPv4Stack=true" with "-Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true"
      7. Save the new settings and start the server
      8. Stop the server - FAIL

      Show
      1. Set up EAP6/AS7 in JBT/JBDS 2. Open the server in server editor (double-click the server in Server view) and change the Host name to your IPv6 address (i.e. ::1 for localhost) 3. In the server editor, click Open launch configuration 4. Uncheck "Always update arguments..." 5. Add this to program arguments field: -b=::1 -bunsecure=::1 -Djboss.default.multicast.address=ff01::1 6. In the VM arguments field, replace "-Djava.net.preferIPv4Stack=true" with "-Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true" 7. Save the new settings and start the server 8. Stop the server - FAIL
    • Hide

      Two options:
      a) Add -bmanagement=<your_ipv6_address> to your launch config or check "Expose your management port..." in server editor
      b) When the server fails to stop on the first attempt, click Stop again and the server will be forced to stop (i.e. the process will be killed)

      Show
      Two options: a) Add -bmanagement=<your_ipv6_address> to your launch config or check "Expose your management port..." in server editor b) When the server fails to stop on the first attempt, click Stop again and the server will be forced to stop (i.e. the process will be killed)

    Description

      When you set up your server to be bound to IPv6 (but you don't bind the management port to anything), the server fails to stop. Second attempt will force the server to stop.

      This is the error in the log:

      !ENTRY org.eclipse.wst.server.core 4 0 2012-07-02 16:49:05.284
!MESSAGE Server jboss-eap-6.0.0.GA failed to stop.

      This happens most probably because in such scenario, the management port is bound to IPv4 localhost (127.0.0.1).

      Indeed I just verified that this is not related to IPv6 specifically but any host name other than localhost - if you don't check "Expose your management port" (and don't set -Dmanagement manually) and the hostname is something else than localhost, then this issue will arise. Note that with remote servers you don't need to bind the management port to anything for server stop to work. So we either need to set -Dmanagement always or make sure it is not needed.

      Attachments

        Issue Links

          is caused by

          Feature Request - Feature requests from customers and/or users JBIDE-19113 wf mgmt jars not working for ipv6: Update wf jars to 8.2 jars

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JBIDE-17173 Local EAP6/AS7 server fails to start properly when hostname is not localhost

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rob.stryker Rob Stryker (Inactive)
              exd-mmalina Martin Malina
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: