activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <>
Subject [jira] [Reopened] (AMQ-4897) Race condition in failover transport
Date Tue, 12 May 2015 20:43:01 GMT


Gary Tully reopened AMQ-4897:
      Assignee: Gary Tully  (was: Dejan Bosanac)

attempting to lock the reconnectMutex in handle transport failure when a write is blocked
results in not being able to timeout the connection. the inactivity monitor blocks leaving
a stalled connection.

> Race condition in failover transport
> ------------------------------------
>                 Key: AMQ-4897
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.9.0
>            Reporter: Dejan Bosanac
>            Assignee: Gary Tully
>             Fix For: 5.9.1, 5.10.0
> There's a small chance of the race condition when using priority backup with extremely
small reconnect delay (0). In that case, the failover transport will get into inconsistent
state. The client will stay connected to the "non-priority" broker, but the priority backup
will not be created due to this inconsistency.
> The solution is to synchronise handling of connection failure with the reconnect mutex.

This message was sent by Atlassian JIRA

View raw message