[
https://jira.jboss.org/browse/JBAS-6144?page=com.atlassian.jira.plugin.sy...
]
Scott Marlow commented on JBAS-6144:
------------------------------------
Would synchronous replication help? With async there is a small window (or it could be
larger depending on the communication channel queue length). If we want to track down the
why, maybe some debug logging in key places would help. Certain applications that require
absolute data integrity would be happier with sync (IMO). Applications that don't
mind a short period of dirty data on the failed over to node, would be happy with async
(but the test probably needs enhancing to properly handle async IMO).
Resolve intermittent
org.jboss.test.cluster.defaultcfg.web.test.ScopedSetAttributeTestCase(Default-udp).testInvalidate
failure
------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6144
URL:
https://jira.jboss.org/browse/JBAS-6144
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Clustering, Web (Tomcat) service
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 6.0.0.Final
This test intermittently fails. The web clustering tests in the default REPL_ASYNC
config can occasionally fail due to timing, where the test fails over to the other cluster
node before the replicated session arrives. There is a 200 ms delay before failover, but
occasional bad luck (e.g. a full gc at wrong time) can make that too short. (Making it
longer makes the whole testsuite longer.) But, this issue should cause random failures,
whereas this particular test seems to pop up as a failure a high percentage of the time.
Need to understand why.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira