Wildfly 10 server doesn't know it's started?

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Wildfly 10 server doesn't know it's started?

jblum
Hi -- I'm seeing a bug which I thought was eliminated in NB 8.1...

I've got a Wildfly 10 instance set up and successfully running outside of NetBeans.  When I try to start it inside NetBeans, from the Services tab, it appears to start successfully -- but NetBeans doesn't recognize that it's actually started, and so any attempts to deploy, debug, or run a project fail.

The Wildfly startup is clearly successful; everything I'd already deployed outside of NetBeans is visible on port 8080, and the startup log displayed in the Output\Wildfly Application Server tab ends with:

22:07:35,877 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
22:07:35,877 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
22:07:35,877 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) started in 53382ms - Started 1569 of 1853 services (484 services are lazy, passive or on-demand)

So it appears to be running okay.  But the icon in the Services\Servers list never updates to show a running symbol, its right-click menu still displays its options as if it were stopped, and any attempts to deploy or run my own project just get the following:

/home/jon/NetBeansProjects/TestWS1/nbproject/build-impl.xml:1152: Deployment error: WildFly Application Server Start Failed. HTTP Connector port 8080 is already in use.
See the server log for details.

So it's not recognizing that the instance currently running on 8080 is the one NetBeans started itself!

To me, this looks suspiciously similar to bug https://netbeans.org/bugzilla/show_bug.cgi?id=262252 , which was supposedly fixed in the 8.1 release.  But I've seen mentions online that Wildfly 10 support isn't stable until NB 8.2 RC1.  Could someone clarify the current state of play?




Reply | Threaded
Open this post in threaded view
|

Re: Wildfly 10 server doesn't know it's started?

ehsavoie
Hi,
WildFly 10 wasn't out by the time NetBeans 8.1 was released so the plugin was using a nightly build of WildFly which explains why the support wasn't correct.
I tried to backport some of the changes required from the NetBeans 8.2 dev branch into 8.1 but it wasn't sufficient (as i had refactored a lot of code in the meanwhile).
The same 'issue' may happen with WildFly 11 (as we are 'far' from a stable WildFly and NetBeans 8.2 is already out).
Cheers,
Emmanuel


On Wed, Nov 2, 2016 at 6:34 AM, jblum <[hidden email]> wrote:
Hi -- I'm seeing a bug which I thought was eliminated in NB 8.1...

I've got a Wildfly 10 instance set up and successfully running outside of NetBeans.  When I try to start it inside NetBeans, from the Services tab, it appears to start successfully -- but NetBeans doesn't recognize that it's actually started, and so any attempts to deploy, debug, or run a project fail.

The Wildfly startup is clearly successful; everything I'd already deployed outside of NetBeans is visible on port 8080, and the startup log displayed in the Output\Wildfly Application Server tab ends with:

22:07:35,877 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on <a href="http://127.0.0.1:9990/management 22:07:35,877" rel="noreferrer" target="_blank">http://127.0.0.1:9990/management
22:07:35,877 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
22:07:35,877 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) started in 53382ms - Started 1569 of 1853 services (484 services are lazy, passive or on-demand)

So it appears to be running okay.  But the icon in the Services\Servers list never updates to show a running symbol, its right-click menu still displays its options as if it were stopped, and any attempts to deploy or run my own project just get the following:

/home/jon/NetBeansProjects/TestWS1/nbproject/build-impl.xml:1152: Deployment error: WildFly Application Server Start Failed. HTTP Connector port 8080 is already in use.
See the server log for details.

So it's not recognizing that the instance currently running on 8080 is the one NetBeans started itself!

To me, this looks suspiciously similar to bug https://netbeans.org/bugzilla/show_bug.cgi?id=262252 , which was supposedly fixed in the 8.1 release.  But I've seen mentions online that Wildfly 10 support isn't stable until NB 8.2 RC1.  Could someone clarify the current state of play?





Reply | Threaded
Open this post in threaded view
|

Wildfly 10 server doesn't know it's started?

jblum
In reply to this post by jblum
Ah, it's good to know that it wasn't just me messing up my system!

I've moved to 8.2 now, and the startup / shutdown issue appears to be resolved.  However, I'm still getting some bits of odd behavior when it starts, because NetBeans starts Wildfly with different settings from the Wildfly instance I'd been running myself as a service outside of NetBeans.  It's using the correct Wildfly standalone config file, but it appears the service runs against a different JDK instance -- still 1.8, but OpenJDK rather than Java HotSpot -- and apparently as a result I'm getting obscure exceptions in another application running on Wildfly.

Long story short, I want to try creating a new Java Platform for the Wildfly Server inside NetBeans, pointing to /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.102-1.b14.el7_2.x86_64 (the one the service uses) rather than /usr/java/latest...  but for some reason, when I go through the Add Platform wizard, it won't recognize the new directory as a platform folder!  Any advice on how to fix that?

Thanks,
Jon Blum




Reply | Threaded
Open this post in threaded view
|

Wildfly 10 server doesn't know it's started?

jblum
In reply to this post by jblum
Never mind, I sorted it out -- the folder which I thought was a JDK was only a JRE, which is why it wasn't showing up!

After installing the full JDK, all the issues appear to be sorted out.

Cheers,
Jon Blum




Reply | Threaded
Open this post in threaded view
|

Re: Wildfly 10 server doesn't know it's started?

icjohnsoia@gmail.com
I can confirm from a freshly installed netbeans8.2 that this problem
persists.

That is:  Netbeans does not recognize that wildfly 10.1 is started.  The
option to start the server is not grayed out.  When pressed the server
gives:  ...port 8080 is already in use. As Per:

"Deployment error: WildFly Application Server Start Failed. HTTP Connector
port 8080 is already in use.
See the server log for details."

Further, attempting to kill the server in the same drop down fails to kill
the server with out any message attached indicating failure.









--
Sent from: http://netbeans-org.1045718.n5.nabble.com/Netbeans-J2EE-f2957935.html
Reply | Threaded
Open this post in threaded view
|

Re: Wildfly 10 server doesn't know it's started?

icjohnsoia@gmail.com
Problem reolved! :)

On Oct 26, 2017 7:36 AM, "[hidden email]" <[hidden email]> wrote:
I can confirm from a freshly installed netbeans8.2 that this problem
persists.

That is:  Netbeans does not recognize that wildfly 10.1 is started.  The
option to start the server is not grayed out.  When pressed the server
gives:  ...port 8080 is already in use. As Per:

"Deployment error: WildFly Application Server Start Failed. HTTP Connector
port 8080 is already in use.
See the server log for details."

Further, attempting to kill the server in the same drop down fails to kill
the server with out any message attached indicating failure.









--
Sent from: http://netbeans-org.1045718.n5.nabble.com/Netbeans-J2EE-f2957935.html