[jbosstools-issues] [JBoss JIRA] (JBIDE-12282) Local AS7/EAP6 fails to stop when bound to IPv6 address or anything but localhost really

[Martin Malina (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-12282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Malina closed JBIDE-12282.
---------------------------------


I tried several different scenarios with WF 8.2 and EAP 6.3 and it all seems to work - start and stop with/without management. I used a hostname bound to ::1 via /etc/hosts.
Verified in both JBDS 8.1.0.Beta1 and 9.0.0.Alpha1.

> Local AS7/EAP6 fails to stop when bound to IPv6 address or anything but localhost really
> ----------------------------------------------------------------------------------------
>
>                 Key: JBIDE-12282
>                 URL: https://issues.jboss.org/browse/JBIDE-12282
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.3.0.Final
>         Environment: JBDS 5.0.0.GA
> Fedora 17 / OS X 10.7 Lion
> JBoss EAP 6.0.0.GA
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
>
> 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:
> {code}
> !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.
> {code}
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)