Version Differences for Increasing Timeouts

(Added in additional info from e-mail.)
Line 1:
- Every command that is sent to an agent and ran, are based on a timeout. If no timely response is received from the agent, [http://wiki.urbancode.com/AnthillPro/Timeout_Expired_Message anthill will timeout the step]. Sometimes these timeouts need to be extended when there are cases such as '''an agent being overloaded with work''' or even when '''a network is too saturated'''. Luckily, the timeout can be modified to a larger number to allow more time to pass, before a job is marked 'dead'.   + Every command that is sent to an agent and ran, are based on a timeout. If no timely response is received from the agent, [http://wiki.urbancode.com/AnthillPro/Timeout_Expired_Message anthill will timeout the step]. Sometimes these timeouts need to be extended when there are cases such as '''an agent being overloaded with work''' or even when '''a network is too saturated'''. Luckily, the timeout can be modified to a larger number to allow more time to pass, before a job is marked 'dead'. The current method of how the timeouts work is below:  
       
    + * Send Command  
    + * Wait for '''defaultTimeout''' for acknowledgement that the command was received  
    + * Loop until command status is "completed":  
    + ** Send Request for command status  
    + ** wait '''cmdResultTimeout''' for status  
       
    + ''NOTE: The agent will try to respond within '''cmdResultTimeout'''/2 milliseconds as a safety margin, but the server will wait the full time!''  
       
  =Server installed.properties=    =Server installed.properties= 
       
Line 9:
       
       
       
       
  =Server system properties=    =Server system properties= 
       
Line 20:
  <pre>com.urbancode.anthill3.announceIntervalMillis=30000    <pre>com.urbancode.anthill3.announceIntervalMillis=30000 
  com.urbancode.anthill3.maxMissedAnnouncements=2</pre>    com.urbancode.anthill3.maxMissedAnnouncements=2</pre>