You can modify the watchdog timeout by changing the connection
timeout time, which is the time a connection can be inactive before a watchdog
message is sent. You can also change the number of consecutive unanswered
watchdog requests that can occur before a connection is placed on a Suspect
Peer Connections List.
About this task
Note: In case of a clustered installation, repeat these steps for
each node in the cluster.
- Open Diameter_Rf.properties, Diameter_Ro.properties,
and Diameter_Sh.properties in a text editor. The files can be found in the following location:


was_profile_root/properties/
Note: was_profile_root is
the directory for a
WebSphere® Application Server
Network Deployment profile
called
profile_name. By default, this directory
is:
/usr/IBM/WebSphere/AppServer/profiles/profile_name
/opt/IBM/WebSphere/AppServer/profiles/profile_name
/opt/IBM/WebSphere/AppServer/profiles/profile_name
For example, AppSrv01 in a standalone environment,
or Custom01 as the name of a federated node profile in a clustered
environment.
- Modify the value of conx.watchDogTimeout to
change the number of seconds a connection can be inactive before Diameter Enabler base sends
a watchdog packet to the peer. Valid values are 0 and any whole integer
between 6 and 2147483647. The default value is 30.
If you set the value to 0, Diameter Enabler base does
not send a watchdog packet to the peer.
- Modify the value
of conx.maxWatchDogExpirations to change the number
of watchdog timeouts after which Diameter Enabler base declares
the connection suspect and starts failover processing to the secondary
connection. The default value is 2. The valid values
are 0, and any value between 2 to 2147483647. If you set this value
to 0, Diameter Enabler base will
suspend the failure monitoring, and it will not start failover processing
on this connection.
Example:
For a setting of 2, when the watchdog timeout occurs, Diameter Enabler will
send the first watchdog request. When the second watchdog timeout
occurs, this connection and the associated routes will start failover
processing.
- Save and close Diameter_Rf.properties, Diameter_Ro.properties,
or Diameter_Sh.properties.
- Restart Rf accounting Web service, Ro online charging Web service,
or Sh subscriber profile Web service.
Example
Example:
con1.watchDogTimeout = 40
con1.maxWatchDogExpirations = 2