Dashboard > GBuild > Home > Configuring the ports and connections > Information > Page Comparison
Configuring the ports and connections
Version 1 by David Blevins
on Jan 06, 2006 23:05.

compared with
Current by David Blevins
on Jan 07, 2006 15:31.

(show comment)
These lines were removed. This word was removed.
These lines were added. This word was added.

View page history

There are 4 changes. View first change.

 h1. The component
 Look for the ClientManager component in the [application.xml] file.
 The ClientManager is just a bunch of code that represents the connection and jms session open with the jms broker (activemq). It's in here as a component so all things that wish to consume or produce mesages can simply have a reference to it and do not need to worry about maintaining or reestablishing connections. The ClientManager establishes a connection to the broker when the Agent starts. If the connection is dropped for some reason, the ClientManager will block all the Agents using it while it tries several times to create a new connection to the broker.
 The ClientManager will also send a ping notification on a ping topic which serves two purposes:
 # It helps to keep the connection alive on networks that automatically close connections it sees as inactive.
 # It allows one to easily see which agents are active in the build network.
 h1. broker-url
  h2. broker-url
 The URL of the JMS broker -- i.e. the thing managing the distributed [Queues and Topics].
h1. ping-interval
  h2. ping-interval
 A value in milliseconds of how often the ClientManager should send a ping message onto the ping topic. A value of 300000 would be 5 minutes.
h1. reconnect-attempts
  h2. reconnect-attempts
 How many attempts in a row without success should the ClientManager try to reconnect before giving up. Something above 3 is strongly advisable. Sometimes the broker needs to be restarted or there is a hiccup in the connection and connections go away for a few seconds or even minutes.
 h1. reconnect-delay
  h2. reconnect-delay
 How long in milliseconds should the ClientManager wait after a failed reconnect attempt before it tries again. Ideally the reconnect-attepmts and reconnect-delay setting should total up to something that gives you at least 10 minutes of tolerance on bad connections. Even 1 hour would be totally fine.
Site running on a free Atlassian Confluence Open Source Project License granted to OSS. Evaluate Confluence today.
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.5.5 Build:#811 Jul 25, 2007) - Bug/feature request - Contact Administrators