This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 256578 - Wildfly starts well but its deployments aren't shown.
Summary: Wildfly starts well but its deployments aren't shown.
Status: VERIFIED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: WildFly (show other bugs)
Version: 8.1
Hardware: PC Linux
: P3 normal (vote)
Assignee: ehsavoie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-13 09:09 UTC by negora
Modified: 2016-02-03 12:33 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description negora 2015-11-13 09:09:44 UTC
I've configured both Wildfly 8.2.0 and Wildfly 9.0.2 in NetBeans IDE 8.1, with the "standalone-full" profile, in the "Services" tab. When I click on the "Start" option on any of them, it starts well (the log output is right), but the "Services" tab doesn't show its deployments.

I can't stop it either, because the "Stop" option looks like attenuated. So you've either to kill the server from the IDE or stop it by hand, from the console.

It's like if the Wildfly plug-in didn't detect that the server is running. Indeed, if you try to run a Java EE project when the server is already running, the IDE will complain telling something like this:

  "wildfly-9 Start Failed. HTTP Connector port 8080 is already in use."

I believe that the bug #256171 could be related to this one.

Thank you.
Comment 1 ehsavoie 2015-11-13 09:13:38 UTC
Did you change the admin port ? Check that netbeans uses 9990 on WF9
Comment 2 negora 2015-11-13 09:33:01 UTC
Thank you for your prompt answer. No, I didn't change the port. It remains at 9990. Furthermore, the installation of Wildfly 9 is a fresh one. Nothing has been altered. At least intentionally.

But I believe that I've found the cause right now. I had installed Wildfly in /usr/local/lib/wildfly-9.0.2/ but I had created a soft link to it in /usr/local/lib/wildfly-9/ . To configure the Wildfly plug-in I'm using the soft link, not the pure directory. I've tried to use the directory and now it's working fine.

I've also done the change with Wildfly 8.2.0 and it has worked fine too.

So my conclusion is that soft links seem to cause problems with the current version of the Wildfly plug-in.
Comment 3 ehsavoie 2015-11-13 10:14:01 UTC
TBH I never tried to use a softlink :o)
Maybe it fails when we are trying to detect to which 'instance' the server matches.
Comment 4 ehsavoie 2015-12-15 08:57:36 UTC
Fixed in changeset 294209:6bf0c1034696
Comment 5 negora 2015-12-15 09:35:21 UTC
Thank you :) .
Comment 6 Quality Engineering 2015-12-16 02:30:51 UTC
Integrated into 'main-silver', will be available in build *201512160002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/6bf0c1034696
User: Emmanuel Hugonnet <ehsavoie@netbeans.org>
Log: Fixing #256578: incorrect wildfly detection when the used path is a softlink.
Comment 7 Jiri Prox 2015-12-17 11:43:13 UTC
verified in trunk
Comment 8 Jiri Kovalsky 2016-01-27 17:57:37 UTC
Emmanuel, can you please integrate this fix to release81 branch by 1/31? Thanks!
Comment 9 ehsavoie 2016-01-27 18:14:02 UTC
Changeset: http://hg.netbeans.org/releases/rev/00ae6e3f574e
User: Emmanuel Hugonnet <ehsavoie@netbeans.org>
Log: Fixing #256578: incorrect wildfly detection when the used path is a softlink.