This reverts commit e5135df.
…e to HV 5" due to JAX-RS breakage This reverts commit 4939e56.
HornetQ failover is depending on the file system to lock a file. I have seen PRs be aborted because HornetQ live server can not lock this file to start (there is no timeout on this lock operation). Deleting the directory ensures that the file system's lock (from previous runs) is removed.
* update maven GAV for JMS API to: org.jboss.spec.javax.jms:jboss-jms-api_2.0_spec:1.0.0.Alpha1 * exclude the JMS 1.1 spec artifact from org.jboss.ws.cxf:jbossws-cxf-server dependencies * exclude temporarily the JMS 1.1 spec artifact from org.hornetq:hornetq-jms-server and org.hornetq:hornetq-jms-client depedencies until HornetQ supports JMS 2.0
This commit adds support for multiplexing the remoting protocol over the HTTP management port, removing the need for two seperate management ports. Port 9999 is now no longer present in the default config, and the management client will attempt to connect via a HTTP upgrade by default.
…s) via jvm arguments Obs: This is working, but the final tests on subsystem.xml fails because the final value is not int. I change the ajp, http, https and remoting. These parameteres can be configurated on Jvm Parameters like that: -Djboss.http.port=9080 -Djboss.https.port=9843 -Djboss.remoting.port=4487 -Djboss.ajp.port=8010 If not set, the default is configurated. This is work OK, but the surefire final test fails on: org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase and org.jboss.as.test.smoke.mgmt.BasicOperationsUnitTestCase We need adjust the tests Too.
…names to use wildfly base name.