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 270791 - Deployment error: Connector port in use when deploying to already running WildFly Server
Summary: Deployment error: Connector port in use when deploying to already running Wil...
Status: NEW
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Infrastructure (show other bugs)
Version: 8.2
Hardware: PC Linux
: P3 normal (vote)
Assignee: Petr Hejl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-02 12:19 UTC by sviatopolk
Modified: 2017-06-02 12:19 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description sviatopolk 2017-06-02 12:19:15 UTC 
Configuration is linux/amd64, Java web project, Ant build.
When trying to run, the following error happens:

ant -f /home/user/NetBeansProjects/JSpringTest -Dnb.internal.action.name=run -Ddirectory.deployment.supported=false -DforceRedeploy=false -Dnb.wait.for.caches=true -Dbrowser.context=/home/user/NetBeansProjects/JSpringTest run
init:
deps-module-jar:
deps-ear-jar:
deps-jar:
library-inclusion-in-archive:
library-inclusion-in-manifest:
compile:
compile-jsps:
Starting WildFly Application Server
WildFly Application Server Start Failed. HTTP Connector port 8080 is already in use.
/home/user/NetBeansProjects/JSpringTest/nbproject/build-impl.xml:1050: Deployment error: WildFly Application Server Start Failed. HTTP Connector port 8080 is already in use.
See the server log for details.
BUILD FAILED (total time: 0 seconds)

WHILST I only had the error with Wildfly 10.1, I picked "Infrastructure" as people seem to have reported similar issues for different platforms, including JBoss and GlassFish versions.

The trouble as I see that there is no option to configure if you ever want to actually start the server or not in project's run configuration, so that it tries to start a server with the same details as one that is already running. Perhaps that is a preferable solution to this issue.

I know that theoretically I could stop the always-running server just to be restarted by NetBeans when it sees fit, and also pick a different configuration for starting another server at a different port, but I don't think this is any good in terms of AoT optimizations or resource questions, respectively.

When I try to do the same with a MAVEN project, it gets the same error, but it ignores it and goes on to deploy the bundle.