Details
-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
7.0.1.Final
-
None
Description
When starting JBossAS 7.0.0.Final with jboss-as-arquillian-container-managed from maven, the JBossAS (even more instances in a cluster) starts smoothly. After updating the version to 7.0.1.Final, the managed container gets stuck when starting first of the JBossAS instances in the cluster. It hangs on "09:39:04,084 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.1.Final "Zap" started in 2570ms - Started 93 of 148 services (55 services are passive or on-demand)"
This is still true with JBossAS 7.1.0.Alpha1-SNAPSHOT (where HEAD = commit 0e3e092eb97d2b3d324ca623db0dabc949a6fbbe - AS7-1697 Add test that verifies methods with arrays in their signature are handled correctly)
I tried various combinations of maven-surefire-plugin (2.9 with forkMode = once, 2.9 with fork mode never, 2.8.1 with fork mode once), none of them works.
The configuration I'm using in arquillian.xml is:
<group qualifier="Grid"> <container qualifier="container1" managed="true"> <protocol type="jmx-as7"> <property name="executionType">REMOTE</property> </protocol> <configuration> <property name="bindAddress">test1</property> <property name="managementPort">9999</property> <property name="jbossHome">/home/mgencur/Java/jboss7/jboss-as-7.0.1.Final</property> </configuration> </container> <container qualifier="container2" managed="false"> <protocol type="jmx-as7"> <property name="executionType">REMOTE</property> </protocol> <configuration> <property name="bindAddress">test2</property> <property name="managementPort">19999</property> <property name="jbossHome">/home/mgencur/Java/jboss7/jboss-as-7.0.1.Final-2</property> </configuration> </container> </group>
Is this a configuration problem?
Attachments
Issue Links
- blocks
-
ARQ-336 Inject container references in the test to start/stop containers
-
- Closed
-
