Thanks for response, that settled it. Default port number did not seemed (to beginner-ish
me) as it's designed to be used with port offsets, so I did not try that. But
providing port number fixed it.
----- Original Message -----
I'd assume that the plugin tries to connect to the server on the
management port to figure out if the server really started. But if you
set a port offset via a system property, the plugin has no chance of
figuring out that the default port is now wrong (short of parsing the
There seems to be a configuration option for specifying the port manually:
I'd start there.
P.S.: I'm not sure if this is the correct list for this type of questions.
On 11.4.2016 10:08, Martin Mucha wrote:
> I'm having problems when using wildfly-maven-plugin with port-offset. If I
> specify pom.xml like below, server does start up, but shutsdown after a
> minute, because it was allegedly not started up (which is not true). When
> server-args are omitted, everything works. If it's like below, everything
> works as well, but only for a minute. Can you advice how correct
> port-offset usage looks like? Thanks.
> wildfly-dev mailing list
wildfly-dev mailing list