[jboss-jira] [JBoss JIRA] (AS7-2837) Using ARQ prevents starting clustering in AS7

[Radoslav Husar (Created) (JIRA)]

Using ARQ prevents starting clustering in AS7
---------------------------------------------

                 Key: AS7-2837
                 URL: https://issues.jboss.org/browse/AS7-2837
             Project: Application Server 7
          Issue Type: Bug
          Components: Clustering, Test Suite
    Affects Versions: 7.1.0.Beta1
            Reporter: Radoslav Husar
            Assignee: Radoslav Husar
            Priority: Blocker


Looks like all the clustering testing are broken.

No idea where is the glitch, but using ARQ prevents clustering from being started. 

ARQ is configured

{code}
        <container qualifier="clustering-udp-0" default="true">
            <configuration>
                <property name="jbossHome">${basedir}/target/jbossas-clustering-udp-0</property>
                <property name="javaVmArguments">${server.jvm.args} -Djboss.inst=${basedir}/target/jbossas-clustering-udp-0</property>
                <property name="serverConfig">standalone-ha.xml</property>
            </configuration>
        </container>
{code}

and ARQ started container says
{code}
17:39:39,123 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) Starting deployment of "distributable.war"
17:39:39,464 INFO  [org.jboss.web] (MSC service thread 1-2) registering web context: /distributable
17:39:39,539 INFO  [org.jboss.as.server.controller] (pool-1-thread-1) Deployed "distributable.war"
17:39:40,940 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped deployment distributable.war in 38ms
17:39:40,987 INFO  [org.jboss.as.server.controller] (pool-1-thread-1) Undeployed "distributable.war"
{code}

but it should indeed say something like 

{code}
17:40:01,657 INFO  [org.jboss.weld] (MSC service thread 1-3) Starting weld service
17:40:01,776 INFO  [org.jboss.web] (MSC service thread 1-2) registering web context: /distributable
17:40:02,387 INFO  [stdout] (MSC service thread 1-2) 
17:40:02,387 INFO  [stdout] (MSC service thread 1-2) -------------------------------------------------------------------
17:40:02,388 INFO  [stdout] (MSC service thread 1-2) GMS: address=rhusar/web, cluster=web, physical address=127.0.0.1:55200
17:40:02,388 INFO  [stdout] (MSC service thread 1-2) -------------------------------------------------------------------
17:40:04,680 WARN  [org.infinispan.config.ConfigurationValidatingVisitor] (MSC service thread 1-3) ISPN000152: Passivation configured without a valid eviction policy. This could mean that the cache store will never get used unless code calls Cache.evict() manually.
17:40:04,816 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-3) ISPN000078: Starting JGroups Channel
17:40:04,820 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-3) ISPN000094: Received new cluster view: [rhusar/web|0] [rhusar/web]
17:40:04,820 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-3) ISPN000079: Cache local address is rhusar/web, physical addresses are [127.0.0.1:55200]
17:40:04,823 INFO  [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-3) ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.0.BETA5
17:40:04,965 INFO  [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-3) ISPN000031: MBeans were successfully registered to the platform mbean server.
17:40:05,043 INFO  [org.jboss.as.clustering] (MSC service thread 1-3) JBAS010301: Started repl cache from web container
17:40:05,069 INFO  [org.jboss.as.clustering.CoreGroupCommunicationService.web] (MSC service thread 1-2) JBAS010207: Number of cluster members: 1
17:40:05,115 INFO  [org.jboss.web] (MSC service thread 1-2) registering web context: /clusterbench
17:40:05,161 INFO  [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "clusterbench-ear.ear"
17:40:05,162 INFO  [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "distributable.war"
...etc
{code}



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira