activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <>
Subject [jira] Resolved: (AMQ-319) ActiveMQ hangs when initial connection to broker fails using reliable transport
Date Tue, 14 Nov 2006 17:24:02 GMT
     [ ]

Hiram Chirino resolved AMQ-319.

    Fix Version/s: 4.0.3
                       (was: 3.2.5)
       Resolution: Fixed
         Assignee: Hiram Chirino

Since you can set a max reconnect attempt in 4.0.. this problem is not an issue there anymore.

>  ActiveMQ hangs when initial connection to broker fails using reliable transport
> --------------------------------------------------------------------------------
>                 Key: AMQ-319
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: JMS client
>    Affects Versions: 3.0
>            Reporter: Ramzi Saba
>         Assigned To: Hiram Chirino
>             Fix For: 4.0.3
> Make these changes in the JMS client to avoid blocking on startup in case all brokers
are down:
> 1- Start the reliable tcp channel in its own thread (seems there was an attempt to do
so anyway)
> 2- Synchronous and asynchronous client calls (via session, consumer, etc.) to the reliable
tcp channel should simply verify if a reliable channel has been already established, else
throw a JMSException, alternatively allow the client to configure a timeout (currently it's
hardcoded for synchronous calls only I believe).
> 3- Other than starting the reliable channel, the client should not be responsible of
reestablishing a lost or unavailable channel. I would delegate reliability to the reliable
channel itself.
> 4- Look into adding a listener to allow for a silent client startup and reconnect behind
the scene once the broker is up

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message