You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Gerbil's QuestionAnswering branch, start.sh has the following argument passed to maven command: -Dcargo.servlet.port=5004
However, I still get the error regarding port 8080 being unavailable:
[INFO] [en3.ContainerRunMojo] Resolved container artifact org.codehaus.cargo:cargo-core-container-tomcat:jar:1.9.11 for container tomcat9x
[INFO] [beddedLocalContainer] Tomcat 9.x Embedded starting...
[WARNING] [beddedLocalContainer] org.codehaus.cargo.container.ContainerException: Port number 8080 (defined with the property cargo.servlet.port) is in use. Please free it on the system or set it to a different port in the container configuration.
[ERROR] Starting container [org.codehaus.cargo.container.tomcat.Tomcat9xEmbeddedLocalContainer@7a5c6d8] failed
org.codehaus.cargo.container.ContainerException: Port number 8080 (defined with the property cargo.servlet.port) is in use. Please free it on the system or set it to a different port in the container configuration.
It seems that even after providing a port through the commandline the codehaus cargo plugin goes and checks availability of the default port first (8080).
The text was updated successfully, but these errors were encountered:
nikit91
changed the title
[Gerbil QA] Port change issue
[QA] Port change issue
Jun 21, 2022
Hello,
In the Gerbil's QuestionAnswering branch,
start.sh
has the following argument passed to maven command:-Dcargo.servlet.port=5004
However, I still get the error regarding port 8080 being unavailable:
For now, I am using a work-around that involves providing the port directly in the
pom.xml
instead ( Ref: https://codehaus-cargo.github.io/cargo/Configuration+properties.html#Configurationproperties-MavenPlugin)It seems that even after providing a port through the commandline the codehaus cargo plugin goes and checks availability of the default port first (8080).
The text was updated successfully, but these errors were encountered: