[wildfly-dev] about using wildfly-maven-plugin with port-offset

[Ladislav Thon]

Hi,

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
string...).

There seems to be a configuration option for specifying the port manually:

https://docs.jboss.org/wildfly/plugins/maven/latest/start-mojo.html#port

I'd start there.

LT

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:
> 
> Hi,
> 
> 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.
> 
> M.
> ———
> 
> 
>     <plugins>
>       <plugin>
>         <groupId>org.wildfly.plugins</groupId>
>         <artifactId>wildfly-maven-plugin</artifactId>
>         <version>${version.wildfly.maven.plugin}</version>
>         <configuration>
>           <jbossHome>${jbossHome}</jbossHome>
>           <serverConfig>standalone.xml</serverConfig>
>           <server-args>
>             <server-arg>-Djboss.socket.binding.port-offset=200</server-arg>
>           </server-args>
>           <filename>${project.build.finalName}.war</filename>
>         </configuration>
>       </plugin>
>     </plugins>
> 
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>