First the comment needs to be outside the property, otherwise it's not detected as a text-only node.
Secondly managementPort has to be set, because while arquillian passes on jboss.socket.binding.port-offset but does not take it into account. Because of port-offset the management port is moved from 9990 to 10127, but it's the runner framework doesn't know that. It gets stuck waiting to confirm server start, but it's looking at port 9990 to check it. And it looks like I've made the patch with tabs, while the rest of the file is spaces. Don't commit it mixed like that. On 23 February 2017 at 13:21, Sanne Grinovero <sa...@hibernate.org> wrote: > Thanks Jordan! > > Can you explain why we need to define the "managementPort" property? > Do you have a link to the issue maybe? > I'd like to understand that better, especially as we have several > other projects to patch. > > Sanne > > On 23 February 2017 at 11:09, Jordan Gigov <colad...@gmail.com> wrote: >> On 23 February 2017 at 12:24, Sanne Grinovero <sa...@hibernate.org> wrote: >>> I think the setup is not perfect yet, as I've reviewed some failure >>> reports and they seem caused by an already running WildFly instance on >>> the same machine. So either we have a bad job configuration somewhere, >>> or a WildFly instance which didn't shut down correctly. >> >> There is a configuration problem with WildFly, partly due to an >> arquillian bug, partly due to a bug in the wildfly-arquillian runner, >> but both can be bypassed using this patch >> http://pastebin.com/q2Nt0Ent _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
