How to stopmissed ActiveSpaces heartbeats.
Article ID: KB0092730
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveSpaces | - |
| Not Applicable | - |
Description
Description:
This article describes a known issue of missed heartbeats in TIBCO ActiveSpaces.
Symptoms:
ActiveSpaces as-agents stops responding with messages like:
Cause:
Some of the causes are:
This article describes a known issue of missed heartbeats in TIBCO ActiveSpaces.
Symptoms:
ActiveSpaces as-agents stops responding with messages like:
1). consecutively missed 3 heartbeats from server
2). hosts_impacted (1) <= cluster_suspend_threshold (-1).. waiting for 30000 msec
Cause:
Some of the causes are:
1. Network latency, the communication between nodes has network issues and they can't respond timely.
2. Machine is too busy with high CPU usage and high memory usage, causing heartbeats that can't respond timely.
Issue/Introduction
How to stopmissed ActiveSpaces heartbeats.
Resolution
1). Check if there are any network issues in the ActiveSpaces cluster and also check if there is enough free RAM and CPU resources.
2). Set the member timeout property. The timeout parameter specifies how many milliseconds DataGrid waits for a member to reconnect if it loses a connection to the metaspace. The default value is 30000 milliseconds (30 seconds).
Feedback
Yes
No
Powered by
