geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Blevins (JIRA)" <...@geronimo.apache.org>
Subject [jira] Closed: (GBUILD-16) Improve GBuild agent JMS reconnect logic
Date Tue, 25 Apr 2006 05:43:06 GMT
     [ http://issues.apache.org/jira/browse/GBUILD-16?page=all ]
     
David Blevins closed GBUILD-16:
-------------------------------

    Resolution: Fixed
     Assign To: David Blevins  (was: Kevan Miller)

The strategy is now:
1. Use ActiveMQ failover with exponential delay maxed at 30min
2. Retry every two hours there after up to four days

The activemq maxDelay will be added to our reconnect times, so actually we have 5 days of
tolerance.


> Improve GBuild agent JMS reconnect logic
> ----------------------------------------
>
>          Key: GBUILD-16
>          URL: http://issues.apache.org/jira/browse/GBUILD-16
>      Project: GBuild
>         Type: Bug

>   Components: agent
>     Versions: 1.0.0
>     Reporter: Kevan Miller
>     Assignee: David Blevins
>     Priority: Minor

>
> The gbuild agent reconnect logic has several problems.
> User configuration settings for reconnect processing are ignored. Max retries and delay
time are all hard-coded. 
> If the initial connection fails, it seems that the client will never connect.
> Also, we should be able to configure agents to attempt to reconnect forever. There should
be some retry backoff scheme or bimodal reconnect interval... 
> I seem to recall that ActiveMQ has similar features in their client api. It might be
simpler to remove what GBuild currently does and use the built-in ActiveMQ support...
>   

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message