NetBeans Forums

 FAQFAQ   SearchSearch   MemberlistMemberlist   RegisterRegister   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
  

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

 
Post new topic   Reply to topic    NetBeans Forums -> Java EE Users
View previous topic :: View next topic  
Author Message
jblum



Joined: 02 Nov 2016
Posts: 3

PostPosted: Wed Nov 02, 2016 5:34 am    Post subject: Wildfly 10 server doesn't know it's started? Reply with quote

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?
Back to top
ehsavoie



Joined: 25 Sep 2009
Posts: 48

PostPosted: Fri Nov 04, 2016 12:44 pm    Post subject: Wildfly 10 server doesn't know it's started? Reply with quote

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

----------
Emmanuel Hugonnet
http://www.ehsavoie.com
http://twitter.com/ehsavoie


On Wed, Nov 2, 2016 at 6:34 AM, jblum <address-removed ([email]address-removed[/email])> wrote:
Quote:
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?




Back to top
jblum



Joined: 02 Nov 2016
Posts: 3

PostPosted: Fri Nov 04, 2016 1:30 pm    Post subject: Re: Wildfly 10 server doesn't know it's started? Reply with quote

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
Back to top
jblum



Joined: 02 Nov 2016
Posts: 3

PostPosted: Sat Nov 05, 2016 4:20 am    Post subject: Re: Wildfly 10 server doesn't know it's started? Reply with quote

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
Back to top
Display posts from previous:   
Post new topic   Reply to topic    NetBeans Forums -> Java EE Users All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB
By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo