[jbosstools-issues] [JBoss JIRA] (JBIDE-24006) Wildfly server adapter does not report error and works inconsistently

[Martin Malina (JIRA)]

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

Martin Malina closed JBIDE-24006.
---------------------------------


This seems to work as expected. I was unable to get the conflict, because the class bound the port on some other host than 127.0.0.1 or my hostname. But if I used 0.0.0.0 for the WildFly server (both -b and -Djboss.bind.address.management), I could see the confict.
In the case of WildFly 11, the server would stop on its own and the new error was thrown in the error log. In the case of WildFly 10, the server will not stop and will remain Started, but you can see the errors in the server log. When I used port 9999 instead of 9990, I could still get the new error with WildFly 11 as expected, but the tooling seem to have a problem with non-standard management ports - I created a new JIRA for that: JBIDE-24233

Closing.

> Wildfly server adapter does not report error and works inconsistently
> ---------------------------------------------------------------------
>
>                 Key: JBIDE-24006
>                 URL: https://issues.jboss.org/browse/JBIDE-24006
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.4.3.Final
>            Reporter: Jeff MAURY
>            Assignee: Rob Stryker
>              Labels: server, server_adapter, wildfly
>             Fix For: 4.4.4.AM2
>
>
> If Wildfly uses 9999 as the management port, then no error is reported but the adapter does not work.
> Here is an except we've got from the customer:
> {noformat}
> I have an important update on this. I think it's mostly good news.
> I debugged the issue via a virtual session with the person that develops the WildFly plugin for NetBeans. What we found out is that the management port I was using, 9999, conflicts with Netty. For context, I had to specify a port override since 9990 commonly conflicts with NVIDIA drivers on Windows. As soon as I used a port other than 9999 and 9990 everything worked absolutely perfectly. As soon as I switch to 9999 everything basically breaks without a real error message indicating the underlying issue. Using 9990 on the other hand clearly indicated a port conflict.
> I tried the same thing on Eclipse with exactly the same results.
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)