[jboss-jira] [JBoss JIRA] Commented: (JBAS-8540) Modify AS 6 and AS 6 testsuite to work with IPv6 addresses

[Richard Achmatowicz (JIRA)]

    [ https://jira.jboss.org/browse/JBAS-8540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564428#comment-12564428 ] 

Richard Achmatowicz commented on JBAS-8540:
-------------------------------------------

24. Quite a number of session related tests were failing on the Hudson run:

org.jboss.test.cluster.defaultcfg.simpleweb.test.AttributeBasedMaxUnreplicatedInterval (fails on IPv6)
org.jboss.test.cluster.defaultcfg.simpleweb.test.BuddyReplicationToPassivatedSession (fails on IPv6 )
org.jboss.test.cluster.defaultcfg.simpleweb.test.BuddyReplicationFailover (fails on IPv6)
org.jboss.test.cluster.defaultcfg.simpleweb.test.ClusteredSessionMemoryLeak (fails on IPv6 )
org.jboss.test.cluster.defaultcfg.simpleweb.test.ClusteredSessionNotificationPolicy (fails on IPv6 )
org.jboss.test.cluster.defaultcfg.simpleweb.test.MultipleWarSingleRedeploy (fails on IPv6)
org.jboss.test.cluster.defaultcfg.simpleweb.test.ReplicationToPassivatedSession (fails on IPv6 )
org.jboss.test.cluster.defaultcfg.simpleweb.test.SessionBasedMaxUnreplicated (fails on IPv6) 

However, these tests would pass on my local machine. Here are some notes from an email exchange:

---------------------------------- notes --------------------------
I found the problem and it is a bug in the tests due to the change
between JBC and ISPN. Here is what happens when we execute
org.jboss.test.cluster.defaultcfg.simpleweb.test.SessionBasedMaxUnreplicatedInterval:

(i) CacheConfigTestSetup, a wrapper for the test case, sets up two Infinispan caches by calling SessionTestUtil.createCacheContainer.
Before these calls, Brian used JGroupsSystemPropertySupport to temporarily set jgroups.bind_addr, jgroups.udp.mcast_addr and
jgroups.udp.mcast_port to values associated with the testsuite's jbosstest.cluster.node1 system property and jbosstest.udpGroup property.
He restores the original values after the caches have been created.

(ii) once the test starts, it calls SessionTestUtil.createManager() to create two instances of org.jboss.web.tomcat.service.session.JBossCacheManager, 
the session managers used in clustering. These are passed the cahces which were created earlier. The calls to createManager are not preceeded and
followed by calls to JGroupsSystemPropertySupport.

The tests then run.

The bug is that the caches are not actually started when CacheConfigTestSetup is called, but they are started when
SessionTestUtil.createManager is called. So the correct system properties are not getting picked up. I'm guessing that this is a change
from JBC behaviour, right Manik?

If I preceed the calls to createManager with JGroupsSystemPropertySupport calls, the caches get intilaised correctly
and the tests pass on QA lab hosts which they did not previously. Looking at the logs, I can see the correct addresses.

I can't explain why the test passed on my machine and not on the QA lab machines. 
---------------------------------- notes --------------------------

Presently discussing this with the clustering guys. In the end, the simplest solution may be to include JGroupsSystemPropertySupport in the per test setup and teardown of all of these tests, to make sure the right p-roperties get picked up by the JBossCacheManagers.
 

> Modify AS 6 and AS 6 testsuite to work with IPv6 addresses
> ----------------------------------------------------------
>
>                 Key: JBAS-8540
>                 URL: https://jira.jboss.org/browse/JBAS-8540
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 6.0.0.M4
>         Environment: All certified platforms.
>            Reporter: Richard Achmatowicz
>            Assignee: Richard Achmatowicz
>             Fix For: TBD
>
>
> Modify AS 6 and the AS 6 testsuite to work with IPv6 addresses.
> The end result should be:
> (i) AS 6 boots cleanly with both IPv4 and IPv6 addresses
> (ii) the AS testsuite and its test cases run cleanly against IPv4 and IPv6 addresses
> This task does not aim to certify that AS 6 is IPv6-compatible or ready. Such a certification may require the development of additional test cases to verify specific features relating to IPv6. For a discussion of such issues, see https://docspace.corp.redhat.com/docs/DOC-47796.
> This work is a precursor to making AS 7 IPv6 compatible.
>  

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