activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <>
Subject [jira] [Resolved] (AMQ-4285) NetworkFailoverTest failing
Date Thu, 31 Jan 2013 14:21:12 GMT


Gary Tully resolved AMQ-4285.

    Resolution: Fixed
      Assignee: Gary Tully

it looks better now.

there are a bunch of pitfalls of request/reply with temps over a network.

temps are not persistent and are tied to the connection that creates them so  failures can
occur when a connection fails.

some appropriate mods to the test

- backup=false in failover - otherwise there is a race between failover restore and broker
teardown of the old connection.
 -- we can loose a replayed temp dest, if it arrives before the remove is complete.

- Broker.setCacheTempDestinations - this helps with reply that occur before the destination
is removed during failover. the cache keeps the message (a form of temp persistence)

- tracking DestinationDoesNotExistException - a reply may fail if it occurs during failover

- tracking dlq due to failed forwards that result from DestinationDoesNotExistException
> NetworkFailoverTest failing 
> ----------------------------
>                 Key: AMQ-4285
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Test Cases
>    Affects Versions: 5.7.0
>            Reporter: Timothy Bish
>            Assignee: Gary Tully
>            Priority: Minor
>             Fix For: 5.8.0
> The test case NetworkFailoverTest is failing most times on my machine, will fail more
often if the message count value is increased. 

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:

View raw message