Failing tests of quickstarts http-binding and rest-binding when executing command: "mvn jboss-as:deploy". The tests should be skipped or jar should be manualy deployed. Following exception occurs during test: Caused by: java.net.BindException: Address already in use at sun.nio.ch.Net.bind0(Native Method) at sun.nio.ch.Net.bind(Net.java:344) at sun.nio.ch.Net.bind(Net.java:336) at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:199) at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) at org.jboss.netty.channel.socket.nio.NioServerBoss$RegisterTask.run(NioServerBoss.java:193) at org.jboss.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:366) at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:290) at org.jboss.netty.channel.socket.nio.NioServerBoss.run(NioServerBoss.java:42) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) Test mechanism Time elapsed: 0.009 sec <<< ERROR!
Is this after the application has already been deployed once? The bump in the version of the jboss-as deploy plugin seems to now include test phase of the Maven lifecycle. We should be able to modify the quickstart to use a config property for the port value in the unit test which is different than the deployed port value. Simple workaround is to use "mvn -DskipTests jboss-as:deploy"
Sorry, ignore the question about the application being deployed once. I misread the bug description and thought this was about the camel netty binding. We can still update the quickstarts to use a system property for test execution which will cause the standalone netty http server used by HTTP and REST to bind to a different port.
This has been fixed for some time; to deploy a QS on EAP execute 'mvn install -Pdeploy'.
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.