[jboss-jira] [JBoss JIRA] Commented: (AS7-1707) jboss-as-arquillian-container-managed gets stuck when starting JBossAS 7.0.1+

Martin Gencur (JIRA) jira-events at lists.jboss.org
Fri Sep 2 07:23:26 EDT 2011


    [ https://issues.jboss.org/browse/AS7-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12625978#comment-12625978 ] 

Martin Gencur commented on AS7-1707:
------------------------------------

Yes, that works:) Thank you, Aslak.

> jboss-as-arquillian-container-managed gets stuck when starting JBossAS 7.0.1+
> -----------------------------------------------------------------------------
>
>                 Key: AS7-1707
>                 URL: https://issues.jboss.org/browse/AS7-1707
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Test Suite
>    Affects Versions: 7.0.1.Final
>            Reporter: Martin Gencur
>            Assignee: Aslak Knutsen
>
> 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:
> {code:xml}
> <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>
> {code} 
> Is this a configuration problem?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-jira mailing list