We're updating the issue view to help you get more done. 

cargo.port.offset sets the port offset twice on WildFly containers (including EAP 7.0)

Description

cargo-maven2-plugin setting the container id wildfly8x and offset other than 0 do not start the web container Undertow properly - It starts with doubled offset given.

For example if defined 1 then it starts with port 8082. If offset defined 100 it will be started with port 8280.

It also can be seen in INFO log outputs.

Example excerpt:

1 2 3 setting cargo.port.offset: 1 # Set HTTP port /socket-binding-group=standard-sockets/socket-binding=http:write-attribute(name=port,value=${jboss.http.port:8081})

but later starting container:

1 [INFO] [talledLocalContainer] 16:50:10,853 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTP listener default listening on [0:0:0:0:0:0:0:0]:8082

also the admin gui is rechable under the wrong port.

Status

Assignee

Karel Suta

Reporter

dux gary

Components

Fix versions

Affects versions

1.6.1

Priority

Major