activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kai Hudalla (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-1779) RA does not reconnect correctly to a failed broker
Date Fri, 06 Jun 2008 14:24:00 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kai Hudalla updated AMQ-1779:
-----------------------------

    Attachment: amq-1779.patch

I have changed the connectWork to loop until it finally gets a connection to the broker instead
of re-scheduling itself after a failed connection attempt. This way, the monitor on connectWork
is kept until the connection succeeds. In order to make this work, the ActiveMQConnectionConsumer
needs to use asyncSendPacket() for registering itself with the consumer to avoid a deadlock
on the connectWork.

The patch also includes David's fix for the prefetchSize calculation in the EndpointWorker.

Kai

> RA does not reconnect correctly to a failed broker
> --------------------------------------------------
>
>                 Key: AMQ-1779
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1779
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Connector
>    Affects Versions: 5.0.0, 5.1.0
>            Reporter: Kai Hudalla
>         Attachments: amq-1779.patch
>
>
> The Resource Adapter does not cleanly reconnect to a failed broker:
> - it uses stale sessions to deliver messages to an Endpoint resulting in messages not
being delivered at all anymore after the connection has been re-established
> - the code for connecting/reconnecting to the broker is not synchronized properly leading
to race conditions/deadlocks in some situations
> Kai

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message