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 245297 - Unable to operate WildFly 8.1.0 server
Summary: Unable to operate WildFly 8.1.0 server
Status: REOPENED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: WildFly (show other bugs)
Version: 8.0.2
Hardware: PC Windows 8 x64
: P3 normal with 2 votes (vote)
Assignee: ehsavoie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-28 06:47 UTC by PavelPscheidl
Modified: 2018-09-20 07:19 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Error message after mave build. (687 bytes, text/plain)
2014-06-28 06:48 UTC, PavelPscheidl
Details
WildFly startup log. (23.69 KB, text/plain)
2014-06-28 06:50 UTC, PavelPscheidl
Details
Netbeans log. (76.77 KB, application/octet-stream)
2014-06-28 10:28 UTC, PavelPscheidl
Details

Note You need to log in before you can comment on or make changes to this bug.
Description PavelPscheidl 2014-06-28 06:47:22 UTC
Plugin version: 1.0.17
NetBeans: Clean Java EE NetBeans 8.0 with only WildFly plugin added.

What works:
1. Installing the plugin.
2. Adding the server.
3. Starting the server.
4. Menu items: View Admin Console, Edit Configuration, Properties, Start Server

What doesn't work:
1. Stop server button is always disabled, even when the server has already started.

2. Kill server button does nothing. Progress bar is shown for a short period of time, then it disappears and the server is still running.

3. Deployment with server off. When I click the run button, WildFly server is started properly, but NetBeans doesn't know the server is already running and tries to run it again, showing this error message:

NetBeans: Deploying on WildFly Application Server
    profile mode: false
    debug mode: false
    force redeploy: true
Starting WildFly Application Server
WildFly Application Server Start Failed. HTTP Connector port 8080 is already in use.

4. Deployment with server on - there is no attemp to start the server again, but after maven clean & build, the same error message as listed in point 3 shows up.
Comment 1 PavelPscheidl 2014-06-28 06:48:34 UTC
Created attachment 147813 [details]
Error message after mave build.
Comment 2 PavelPscheidl 2014-06-28 06:50:21 UTC
Created attachment 147814 [details]
WildFly startup log.
Comment 3 ehsavoie 2014-06-28 10:21:30 UTC
Which version of the plugin do you use ?
Could you copy alos your netbeans log (from c:\Users\...\.netbeans)
Comment 4 PavelPscheidl 2014-06-28 10:28:20 UTC
Created attachment 147816 [details]
Netbeans log.
Comment 5 PavelPscheidl 2014-06-28 10:29:43 UTC
Plugin version: 1.0.17. I now managed to deploy the war with this scenario:

Kill WildFly server manually -> Restart NetBeans -> click RUN. This way the war is deployed. But the second deploy fails with the same error as mentioned above.

log attached.
Comment 6 ehsavoie 2014-06-28 10:33:40 UTC
Netbeans can't connect to your running instance :
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://localhost:9990. The connection timed out

Do you have some proxy set, some firewall or have you change the default config of WildFly ?
Comment 7 ehsavoie 2014-06-28 10:34:53 UTC
I have seen 'similar' errors with the mysql driver.
Could you attache your WildFly configuration with the datasource ?
Comment 8 PavelPscheidl 2014-06-28 10:47:19 UTC
It was the port Issue. I changed management ports in standalone config. I thought ports are automatically reconfigured.
Comment 9 ehsavoie 2014-06-28 10:53:25 UTC
No, as this can be changed throught the port-offset, thus simple parsing wouldn't help and I didn't want to add another configuration entrey in the wizard.
Comment 10 PavelPscheidl 2014-06-28 10:57:50 UTC
Personally, I think the plugin GUI is very clean & super easy to navigate. Management port setting is something one can definitely leave alone on localhost where you have all the power, but sometimes there are remote test servers one has to operate with. This is just a suggestion for a new feature.
Comment 11 ehsavoie 2014-06-30 17:02:07 UTC
Enhancement https://netbeans.org/bugzilla/show_bug.cgi?id=245329 created.
Now time to code ;)
Comment 12 whbogado 2015-01-02 14:04:25 UTC
The plugin only works when Wildfly is running on the default management port (9990). Unfortunately nVidia network service uses this port so to user the plugin  I had to kill the nVidia process.
It seems that it is necessary to allow the plugin to work on non-default ports. Since Wildfly can run on any port the plugin seems incomplete without this enhancement.
Comment 13 ehsavoie 2015-01-02 15:43:32 UTC
Use the nightly build to before reopening this issue.
Comment 14 Geoff_C 2015-02-19 03:22:21 UTC
I have downloaded the nightly build 201502180001, imported settings from 8.0.1 (updated to 8.0.2), and when I try to add a server it tells me there are no server plugins. Under plugins WildFly is no longer available, nor is it in the installed plugins tab. I did not import the plugins from prior version as that would defeat the purpose of updating the plugin.

The same applies if I delete the userdir and re-run without importing the settings.

Is there a way to get the nightly build of just the plugin?
Comment 15 tlamatiniisrael 2017-01-29 04:20:14 UTC
Hi everyone.

I change the port by default 8080 to 8888 and it worked !!!
Comment 16 ntala 2018-09-20 07:19:49 UTC
2018,fresh copies

I run as debug... "WildFly Application Server Start Failed. HTTP Connector port 8080 is already in use."

wildfly 14

dont mark as fixed, please. that's a lie