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 246559

Summary: Deploy war fails if not using default ports
Product: serverplugins Reporter: jomu <jomu>
Component: WildFlyAssignee: ehsavoie <ehsavoie>
Status: RESOLVED FIXED    
Severity: normal    
Priority: P4    
Version: 8.0.1   
Hardware: PC   
OS: Linux   
Issue Type: DEFECT Exception Reporter:
Bug Depends on: 245329    
Bug Blocks:    
Attachments: config window

Description jomu 2014-08-19 19:31:11 UTC
I configured Wildfly 8.1.0 final to run on port 8088 instead default port 8080.
When adding the server to netbeans I configured port 8088 also. But when deploying, the plugin seems to use the wrong port:

NetBeans: Deploying on wildfly-deployer:localhost:8080#standalone&/path/to/wildfly
    profile mode: false
    debug mode: false
    force redeploy: true

Then nothing happens in Netbeans. Also Wildfly server.log does not show any changes.
Comment 1 ehsavoie 2014-08-20 06:38:39 UTC
I can't reproduce your issue.
The only port that the plugin needs currently is the administrative port: 9990 which is not configurable in netbeans (this is a missing feature).
Changing the HTTP binding port is working just fine as it is used only to create the url sent to your browser.
Comment 2 jomu 2014-08-20 15:51:42 UTC
Hi, 

thanks for the quick reply. 

I can now reproduce it also on Windows. The key is to the change the port to another port like 8088 when you add the server. (see attached screenshot).

Config window 8080, standalone-full.xml 8080 --> works
Config window 8088, standalone-full.xml 8088 --> does not work
Config window 8080, standalone-full.xml 8088 --> works
Config window 8088, standalone-full.xml 8080 --> does not work

So basically you must not touch the value inside the config window - but it seems also to have no effect. If it works, the server runs on the port which is given in the standalone.xml

Lowering to P4 - leaving the config window to 8080 is an easy workaround.
Comment 3 jomu 2014-08-20 15:52:26 UTC
Created attachment 148796 [details]
config window
Comment 4 ehsavoie 2014-08-20 15:56:08 UTC
Are you stopping the server before each change in config ? If you modify the xml file while the server is running your conf won't get saved.
Like I said the HTTP port is not used for deployment, so this shouldn't have any impact.
I've tested on GNU/Linux without reproducing your issue on current nightly build.
Comment 5 jomu 2014-08-20 16:01:12 UTC
Hi,

yes. Stop the server, remove it from Servers, Add new Server, restart/redeploy

Adding the server new is the only way to get the value changed in the config window - I did not find it anywhere else.

Plugin version 1.0.17