2 Replies Latest reply on Jun 18, 2019 9:36 AM by Izak van Langevelde

    Unable to start/stop server from Eclipse Servers tab?

    Izak van Langevelde Newbie

      Running Ubuntu 18.4.02, Widfly 17.0.0 Final, Eclipse 2019-03 (4.11.0).
      I can manage my Wildfly service from the command line, but my Eclipse Servers tab insists the server is stopped, and I cannot start/stop it from there; error messages show no details.
      Looks like eclipse doesn't have a clue about Wildfly, and I don't have a clue on how to proceed. Any guidance here is appreciated...

        • 1. Re: Unable to start/stop server from Eclipse Servers tab?
          Robert Stryker Newbie

          Can you include a screenshot of the error message here?

           

          The eclipse server view generally only knows about servers it started. IF the server was started outside of eclipse, or somehow survived an eclipse restart, the IDE won't have a reference to the old pid / process id, so it can't communicate to it. It also won't be able to start a new one, since a process is already using those ports. And obviously since the 'server adapter' is marked as stopped, it can't terminate the existing process, again because it doesn't have a reference to teh process id.

          • 2. Re: Unable to start/stop server from Eclipse Servers tab?
            Izak van Langevelde Newbie

            I'm one step further. I discovered there was a rogue Wildfly process running, inaccessible from the Ubuntu service interface. This was fixed by a reboot.

             

            Now, I can start/stop a Wildfly server from the Eclipse Servers tab. So far, so good. Now I configured the server as having its life cycle externally managed. While the server status can be accessed from its 8080 port, the server status in eclipse is not correct. Also, a context menu suggests I can still stop the server from Eclipse, which makes no sense. Is this still under construction?

             

            Is there any detailed documentation available on eclipse-wildfly communication? Contrary to your suggestion, process id's don't seem to play a role here, as these are not relevant for controlling Ubuntu services.