[jboss-jira] [JBoss JIRA] (AS7-4006) TS clustering: failures when testing with IPv6
Radoslav Husar (JIRA)
jira-events at lists.jboss.org
Fri Mar 2 08:08:37 EST 2012
[ https://issues.jboss.org/browse/AS7-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673153#comment-12673153 ]
Radoslav Husar commented on AS7-4006:
-------------------------------------
I am seeing this logging though
{noformat}
14:03:57,227 WARNING [org.jgroups.protocols.UDP] (pool-14-thread-1) could not bind to /ff02:0:0:0:0:0:0:1 (IPv6 address); make sure your mcast_addr is of the same type as the preferred IP stack (IPv4 or IPv6) by checking the value of the system properties java.net.preferIPv4Stack and java.net.preferIPv6Addresses.
Will ignore mcast_addr, but this may lead to cross talking (see http://www.jboss.org/community/docs/DOC-9469 for details).
Exception was: java.net.SocketException: Invalid argument
{noformat}
The command used to start the as was:
{noformat}
[rhusar at rhusar standalone]$ /home/rhusar/tools/jdk1.6.0/bin/java -Xmx512m -XX:MaxPermSize=256m -Djboss.dist=/home/rhusar/git/jboss-as/testsuite/integration/clust/../../../build/target/jboss-as-7.1.1.Final-SNAPSHOT -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true -Dts.tr.fsio=100 -Dts.tr.netio=100 -Dts.tr.memio=100 -Dts.tr.db=100 -Dnode0=1:222:68ff:fe0b::1 -Dnode1=1:222:68ff:fe0b::2 -DudpGroup=ff02::1 -Djbossas.ts.submodule.dir=/home/rhusar/git/jboss-as/testsuite/integration/clust -Djbossas.ts.integ.dir=/home/rhusar/git/jboss-as/testsuite/integration/clust/.. -Djbossas.ts.dir=/home/rhusar/git/jboss-as/testsuite/integration/clust/../.. -Djbossas.project.dir=/home/rhusar/git/jboss-as/testsuite/integration/clust/../../.. -Djboss.dist=/home/rhusar/git/jboss-as/testsuite/integration/clust/../../../build/target/jboss-as-7.1.1.Final-SNAPSHOT -Djboss.inst=/home/rhusar/git/jboss-as/testsuite/integration/clust/target/jbossas-clustering-udp-0 -Djboss.node.name=node-udp-0 -ea -Djboss.home.dir=/home/rhusar/git/jboss-as/testsuite/integration/clust/target/jbossas-clustering-udp-0 -Dorg.jboss.boot.log.file=/home/rhusar/git/jboss-as/testsuite/integration/clust/target/jbossas-clustering-udp-0/standalone/log/boot.log -Dlogging.configuration=file:/home/rhusar/git/jboss-as/testsuite/integration/clust/target/jbossas-clustering-udp-0/standalone/configuration/logging.properties -Djboss.modules.dir=/home/rhusar/git/jboss-as/build/target/jboss-as-7.1.1.Final-SNAPSHOT/modules -Djboss.bundles.dir=/home/rhusar/git/jboss-as/build/target/jboss-as-7.1.1.Final-SNAPSHOT/bundles -jar /home/rhusar/git/jboss-as/testsuite/integration/clust/target/jbossas-clustering-udp-0/jboss-modules.jar -mp /home/rhusar/git/jboss-as/testsuite/integration/clust/../../../build/target/jboss-as-7.1.1.Final-SNAPSHOT/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -server-config standalone-ha.xml
{noformat}
and had correctly defined preferred stack.
What is causing this?
> TS clustering: failures when testing with IPv6
> ----------------------------------------------
>
> Key: AS7-4006
> URL: https://issues.jboss.org/browse/AS7-4006
> Project: Application Server 7
> Issue Type: Bug
> Components: Clustering, Test Suite
> Affects Versions: 7.1.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: 7.1.2.Final
>
> Attachments: TEST-org.jboss.as.test.clustering.cluster.ejb3.deployment.ClusteredBeanDeploymentTestCase.xml, TEST-org.jboss.as.test.clustering.cluster.ejb3.stateful.remote.failover.dd.RemoteEJBClientDDBasedSFSBFailoverTestCase.xml, TEST-org.jboss.as.test.clustering.cluster.ejb3.stateful.remote.failover.RemoteEJBClientStatefulBeanFailoverTestCase.xml, TEST-org.jboss.as.test.clustering.cluster.ejb3.stateful.StatefulFailoverTestCase.xml, TEST-org.jboss.as.test.clustering.cluster.ejb3.StatefulTimeoutTestCase.xml, TEST-org.jboss.as.test.clustering.cluster.ejb3.stateless.RemoteStatelessFailoverTestCase.xml, TEST-org.jboss.as.test.clustering.cluster.ejb3.xpc.StatefulWithXPCFailoverTestCase.xml, TEST-org.jboss.as.test.clustering.cluster.jsf.JSFFailoverTestCase.xml, TEST-org.jboss.as.test.clustering.cluster.singleton.SingletonTestCase.xml, TEST-org.jboss.as.test.clustering.cluster.web.ClusteredWebTestCase.xml, TEST-org.jboss.as.test.clustering.cluster.web.DistributionWebFailoverTestCase.xml, TEST-org.jboss.as.test.clustering.cluster.web.ReplicationWebFailoverTestCase.xml
>
>
> {noformat}
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.as.test.clustering.cluster.jsf.JSFFailoverTestCase
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 64.847 sec
> Running org.jboss.as.test.clustering.cluster.ejb3.xpc.StatefulWithXPCFailoverTestCase
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 36.332 sec <<< FAILURE!
> Running org.jboss.as.test.clustering.cluster.ejb3.deployment.ClusteredBeanDeploymentTestCase
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 20.028 sec
> Running org.jboss.as.test.clustering.cluster.ejb3.StatefulTimeoutTestCase
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 32.318 sec
> Running org.jboss.as.test.clustering.cluster.ejb3.stateless.RemoteStatelessFailoverTestCase
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 50.459 sec
> Running org.jboss.as.test.clustering.cluster.ejb3.stateful.StatefulFailoverTestCase
> Tests run: 4, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 70.141 sec <<< FAILURE!
> Running org.jboss.as.test.clustering.cluster.ejb3.stateful.remote.failover.RemoteEJBClientStatefulBeanFailoverTestCase
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 33.873 sec
> Running org.jboss.as.test.clustering.cluster.ejb3.stateful.remote.failover.dd.RemoteEJBClientDDBasedSFSBFailoverTestCase
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 33.836 sec
> Running org.jboss.as.test.clustering.cluster.web.ReplicationWebFailoverTestCase
> Tests run: 4, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 29.568 sec <<< FAILURE!
> Running org.jboss.as.test.clustering.cluster.web.DistributionWebFailoverTestCase
> Tests run: 4, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 29.228 sec <<< FAILURE!
> Running org.jboss.as.test.clustering.cluster.web.ClusteredWebTestCase
> Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 26.916 sec <<< FAILURE!
> Running org.jboss.as.test.clustering.cluster.singleton.SingletonTestCase
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 44.597 sec
> Results :
> Failed tests: testBasicXPC(org.jboss.as.test.clustering.cluster.ejb3.xpc.StatefulWithXPCFailoverTestCase): 3. stopped deployment on node1, xpc should failover to node2, node2 should be able to read entity from xpc(didn't get http success code) expected:<200> but was:<500>
> testRestart(org.jboss.as.test.clustering.cluster.ejb3.stateful.StatefulFailoverTestCase): expected:<20050505> but was:<20010101>
> testRedeploy(org.jboss.as.test.clustering.cluster.ejb3.stateful.StatefulFailoverTestCase): expected:<20050505> but was:<20010101>
> testGracefulSimpleFailover(org.jboss.as.test.clustering.cluster.web.ReplicationWebFailoverTestCase): Session failed to replicate after container 1 was shutdown. expected:<3> but was:<1>
> testGracefulUndeployFailover(org.jboss.as.test.clustering.cluster.web.ReplicationWebFailoverTestCase): Session failed to replicate after container 1 was shutdown. expected:<3> but was:<1>
> testGracefulSimpleFailover(org.jboss.as.test.clustering.cluster.web.DistributionWebFailoverTestCase): Session failed to replicate after container 1 was shutdown. expected:<3> but was:<1>
> testGracefulUndeployFailover(org.jboss.as.test.clustering.cluster.web.DistributionWebFailoverTestCase): Session failed to replicate after container 1 was shutdown. expected:<3> but was:<1>
> testSessionReplication(org.jboss.as.test.clustering.cluster.web.ClusteredWebTestCase): expected:<3> but was:<1>
> Tests run: 38, Failures: 8, Errors: 0, Skipped: 0
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] JBoss Application Server Test Suite: Aggregator ... SUCCESS [10.593s]
> [INFO] JBoss Application Server Test Suite: Integration .. SUCCESS [2.129s]
> [INFO] JBoss Application Server Test Suite: Integration - Clustering FAILURE [8:02.830s]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 8:16.709s
> [INFO] Finished at: Fri Mar 02 13:38:16 CET 2012
> [INFO] Final Memory: 67M/713M
> [INFO] ------------------------------------------------------------------------
> {noformat}
--
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
More information about the jboss-jira
mailing list