-
1. Re: Arquillian with JBoss EAP 6.2.2.GA
bmajsak Jul 11, 2014 7:09 AM (in response to nikhilraj)Hi,
this is interesting, as it should be compatible I guess. Since you are using EAP you can check with RedHat support, but in the meantime can you share your config so that I can have a look if there is something missing?
Cheers,
Bartosz
-
2. Re: Re: Arquillian with JBoss EAP 6.2.2.GA
nikhilraj Nov 19, 2014 6:59 AM (in response to bmajsak)Sorry for such a late response!
Work forced me away and have now dumped me right back in this.
My arquillian.xml contains
<arquillian xmlns="http://jboss.org/schema/arquillian" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=" http://jboss.org/schema/arquillian http://jboss.org/schema/arquillian/arquillian_1_0.xsd"> <container qualifier="jbossas-managed" default="true"> <configuration> <property name="serverConfig">..\..\jvm9\configuration\standalone.xml</property> <property name="outputToConsole">true</property> <property name="managementPort">10449</property> </configuration> </container> </arquillian>
And my standalone.xml contains
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:450}"> <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}" /> <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}" /> <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9443}" /> <socket-binding name="ajp" port="15000" /> <socket-binding name="http" port="15001" /> <socket-binding name="https" port="15002" /> <socket-binding name="jacorb" interface="unsecure" port="15003" /> <socket-binding name="jacorb-ssl" interface="unsecure" port="15004" /> <socket-binding name="messaging" port="15011" /> <socket-binding name="messaging-throughput" port="15013" /> <socket-binding name="modcluster" port="15014" /> <socket-binding name="remoting" port="15015" /> <socket-binding name="txn-recovery-environment" port="15016" /> <socket-binding name="txn-status-manager" port="15017" /> <outbound-socket-binding name="mail-smtp"> <remote-destination host="localhost" port="25" /> </outbound-socket-binding> </socket-binding-group>
The server is started up correctly by Arquillian. But then the tests timeout with the error that the server failed to start.
-
3. Re: Arquillian with JBoss EAP 6.2.2.GA
kpiwko Nov 20, 2014 2:24 AM (in response to nikhilraj)Hi Nikhil,
please make sure you're using Arquillian version certified for EAP 6.2.2, that is you use following BOM to manage your dependencies:
You can setup enterprise repository by following:
Also, make sure that you enable Servlet 3.0 protocol in arquillian.xml.
You can be inspired here:
http://www.jboss.org//quickstarts/eap/tasks/index.html
https://github.com/jboss-developer/jboss-eap-quickstarts/tree/6.2.0.GA/kitchensink
If you'll still struggling to set it up, please provide output of mvn dependency:tree and output of tests with -Darquillian.debug=true flag. Or even better, contact official support location.
Cheers,
Karel