[ http://issues.apache.org/jira/browse/GBUILD-16?page=all ]
David Blevins updated GBUILD-16:
--------------------------------
Summary: Improve GBuild agent JMS reconnect logic (was: GBuild agent JMS
reconnect logic is incorrect)
The activemq feature could potentially be our aggressive reconnect strategy and
the current code (sans the two hard-coded values) could maybe be used for the
more passive mode. Maybe change the delay setting to minutes.
I can verify that the reconnect logic and synchronization around it all work.
> 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: Kevan Miller
> 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
