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

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-24006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13384088#comment-13384088 ] 

Rob Stryker commented on JBIDE-24006:
-------------------------------------

Steps to replicate:

1) Start a server on port 9990. Easiest way is to run a simple java class:

{code}
public class DateServer {
    public static void main(String[] args) throws IOException {
        ServerSocket listener = new ServerSocket(9990);
        try {
            while (true) {
                Socket socket = listener.accept();
                try {
                    PrintWriter out =
                        new PrintWriter(socket.getOutputStream(), true);
                    out.println(new Date().toString());
                    System.out.println("Doin' a business");
                } finally {
                    socket.close();
                }
            }
        }
        finally {
            listener.close();
        }
    }
}
{code}

Step 2: Start WF or EAP server that requires use of port 9990.  Server gets set to 'starting', and console shows output. 
Step 3: Note that the server terminates itself. It failed to start up successfully, and so aborted. Older servers may not do this. They may stay up despite having no services capable of loading. But WF11 (and some earlier ones, not sure which) will terminate themselves automatically. 
Step 4: Note that the error log view has no clear error listed, and no error dialog pops up. 

Suggested new error string for this case: TERMINATED_PREMATURE=Server processes have terminated prematurely. Please check your server logs for more details. 

This string will only be used if the server is switched from 'starting' to 'stopped' with no poller or other mechanism ever accepting the server as started. 


> 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)