[JBoss JIRA] Created: (JBAS-6144) Resolve intermittent org.jboss.test.cluster.defaultcfg.web.test.ScopedSetAttributeTestCase(Default-udp).testInvalidate failure
12:18 p.m.
Resolve intermittent
org.jboss.test.cluster.defaultcfg.web.test.ScopedSetAttributeTestCase(Default-udp).testInvalidate
failure
------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6144
URL: https://jira.jboss.org/jira/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: JBossAS-5.0.1.CR1
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/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:21 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-6144) Resolve intermittent org.jboss.test.cluster.defaultcfg.web.test.ScopedSetAttributeTestCase(Default-udp).testInvalidate failure
[
https://jira.jboss.org/jira/browse/JBAS-6144?page=com.atlassian.jira.plug...
]
Brian Stansberry updated JBAS-6144:
-----------------------------------
Fix Version/s: JBossAS-5.2.0.Beta1
(was: JBossAS-5.1.0.Beta1)
Resolve intermittent
org.jboss.test.cluster.defaultcfg.web.test.ScopedSetAttributeTestCase(Default-udp).testInvalidate
failure
------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6144
URL: https://jira.jboss.org/jira/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: JBossAS-5.2.0.Beta1
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/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:04 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-6144) Resolve intermittent org.jboss.test.cluster.defaultcfg.web.test.ScopedSetAttributeTestCase(Default-udp).testInvalidate failure
[
https://jira.jboss.org/jira/browse/JBAS-6144?page=com.atlassian.jira.plug...
]
Jason T. Greene updated JBAS-6144:
----------------------------------
Fix Version/s: JBossAS-6.0.0.Alpha1
(was: JBossAS-5.2.0.Beta1)
Resolve intermittent
org.jboss.test.cluster.defaultcfg.web.test.ScopedSetAttributeTestCase(Default-udp).testInvalidate
failure
------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6144
URL: https://jira.jboss.org/jira/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: JBossAS-6.0.0.Alpha1
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/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:41 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-6144) Resolve intermittent org.jboss.test.cluster.defaultcfg.web.test.ScopedSetAttributeTestCase(Default-udp).testInvalidate failure
[
https://jira.jboss.org/jira/browse/JBAS-6144?page=com.atlassian.jira.plug...
]
Brian Stansberry updated JBAS-6144:
-----------------------------------
Fix Version/s: JBossAS-6.0.0.M4
(was: JBossAS-6.0.0.M3)
Resolve intermittent
org.jboss.test.cluster.defaultcfg.web.test.ScopedSetAttributeTestCase(Default-udp).testInvalidate
failure
------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6144
URL: https://jira.jboss.org/jira/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: JBossAS-6.0.0.M4
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/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:55 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-6144) Resolve intermittent org.jboss.test.cluster.defaultcfg.web.test.ScopedSetAttributeTestCase(Default-udp).testInvalidate failure
[
https://jira.jboss.org/browse/JBAS-6144?page=com.atlassian.jira.plugin.sy...
]
Brian Stansberry updated JBAS-6144:
-----------------------------------
Fix Version/s: 6.0.0.Final
(was: 6.0.0.M4)
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
3:56 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-6144) Resolve intermittent org.jboss.test.cluster.defaultcfg.web.test.ScopedSetAttributeTestCase(Default-udp).testInvalidate failure
[
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
4:36 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-6144) Resolve intermittent org.jboss.test.cluster.defaultcfg.web.test.ScopedSetAttributeTestCase(Default-udp).testInvalidate failure
[
https://jira.jboss.org/browse/JBAS-6144?page=com.atlassian.jira.plugin.sy...
]
Brian Stansberry commented on JBAS-6144:
----------------------------------------
This test later gets re-run using REPL_SYNC. I don't want to move many tests to purely
REPL_SYNC, no REPL_ASYNC coverage because our standard config is REPL_ASYNC and I think we
need to test things that way I would love it if our test infrastructure could support
async replication but without sleeps. JBC testsuite had a mechanism for doing that
(involved listeners to track when replication messages arrived) but that was based on all
nodes in the cluster + the test driver running in the same VM. AS clustering testsuite has
some tests that work that way (in o.j.test.cluster.defaultcfg.simpleweb.test package) but
most are true integration tests where there are 2 AS processes and a remove test driver.
The above comment is about the general issue of how to make the clustering testsuite more
robust. The specific issue here is this particular test method seemed to fail more often.
TBH, I'm not sure if that is still the case; this JIRA might be out of date. Before
spending much effort chasing this particular failure, it's probably worthwhile to
track the testsuite results for a while and see if it still pops up.
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
10:26 p.m.
New subject: [JBoss JIRA] Closed: (JBAS-6144) Resolve intermittent org.jboss.test.cluster.defaultcfg.web.test.ScopedSetAttributeTestCase(Default-udp).testInvalidate failure
[
https://jira.jboss.org/browse/JBAS-6144?page=com.atlassian.jira.plugin.sy...
]
Shelly McGowan closed JBAS-6144.
--------------------------------
Fix Version/s: (was: 6.0.0.Final)
Resolution: Out of Date
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
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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5086
days inactive
5852
days old
7 comments
4 participants
participants (4)
-
Brian Stansberry (JIRA) -
Jason T. Greene (JIRA)
-
Scott Marlow (JIRA)
-
Shelly McGowan (JIRA)