[
https://issues.apache.org/jira/browse/QPID-4944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700146#comment-13700146
]
ASF subversion and git services commented on QPID-4944:
-------------------------------------------------------
Commit 1499789 from [~aconway]
[ https://svn.apache.org/r1499789 ]
QPID-4944: HA Sporadic failure: test_failover_send_receive
Test failing if run as: ha_tests.py -DDURATION=2
AssertionError: Stalled test0 waiting for 248, sent 1228
The problem was a missing call to notify() when a ReplicatingSubscription
skipped a message. That resulted in very long (>1s) delays between skipped
messages which caused the test to time out.
Changes:
- ReplicatingSubscription::deliver call notify() to keep consumer active.
- Re-enable test_failover_send_receive.
- Increase default credit for replicating subscription to match qpid-send.
- Rename ReplicatingSubscription::unacked as unready, clearer meaning.
> HA Sporadic failure in ha_tests: test_failover_send_receive and
> test_expected_backup_timeout
> ---------------------------------------------------------------------------------------------
>
> Key: QPID-4944
> URL: https://issues.apache.org/jira/browse/QPID-4944
> Project: Qpid
> Issue Type: Bug
> Reporter: Alan Conway
> Assignee: Alan Conway
> Fix For: 0.23
>
>
> Rare sporadic failures in:
> ha_tests.RecoveryTests.test_expected_backup_timeout
> AssertionError: 'recovering' != 'active
> ha_tests.LongTests.test_failover_send_receive
> AssertionError: Broker<006:cluster1-1.log qpidd-26 :44493>
> expected='ready', actual='catchup'
> To reproduce you need to run ha_tests.py in a loop overnight or longer.
> See also: https://bugzilla.redhat.com/show_bug.cgi?id=969039
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
