Properties with On-Premises Agent

Sometimes due to network disruptions (for example, VM restarts), the on-premises agent may appear as healthy, but unable to process any runtime messages. Also, reactivation and testing the connection fails. Under these circumstances. It is recommended that you add the following parameters when starting the agent.

-Dweblogic.http.client.defaultReadTimeout=10000 
-Dweblogic.http.client.defaultConnectTimeout=2000

If you want to use these parameters for an existing on-premises agent installation, you must edit the startAgent.sh file found under the AGENT_INSTALL_DIR directory.

  1. Open startAgent.sh.

  2. Find the following section.

    cd $DOMAIN_HOME/bin     
    ./startWebLogic.sh
  3. Include the following parameters above this section:

    export JAVA_OPTIONS="${JAVA_OPTIONS}  
    -Dweblogic.http.client.defaultReadTimeout=10000  
    -Dweblogic.http.client.defaultConnectTimeout=2000"
    
    cd $DOMAIN_HOME/bin     
    ./startWebLogic.sh
  4. Save and close the file.

  5. Stop and restart the on-premises agent under AGENT_INSTALL_DIR:

    ./stopAgent.sh 
    ./startAgent.sh

Note:

If a small number of connection time out errors remain, increase the value (for example, from 2 seconds to 10 seconds):

-Dweblogic.http.client.defaultConnectTimeout=10000