Why do we sometimes see duplicate Durables when running BW from Admin?
Article ID: KB0090856
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks | - |
| Not Applicable | - |
Description
Resolution:
Here are the reasons you might see duplicate durables:
1) This Could be happening because there is a JMS Queue Subscriber and JMS Topic Durable Subscriber in one engine and both are using same JMS Connection - this is a know issue (Defect ID 1-6X3LX1) - please >> make sure that they both uses their own JMS Connection and in Advanced tab take out the appropriate Connection Factory.
2) Use Client ID if you haven't already - The Client ID is set in the 'JMS Connection' palette.
The durable subscription name that is created in TIBCO EMS has the following format:
<Client ID>:<Durable Subscription>
If the Client ID is left blank, BW drives a name based on the 'JMS Connection' name and the 'BW project' name. This drived name is used as a Client ID and has the following structure 'BW-<JMS Connection name in BW>-<BW Project Name>'
3) We have seen a case while primary engine is going down, the stand by engine will get activate; as the results, duplicate durables get created. To ensure the primary engine shutdown completely, please add the following properties to your deployed TRA file:
- Heartbeat Interval (ms) The master engine of a fault-tolerant group broadcasts heartbeat messages to inform the other group members that it is still active. The heartbeat interval determines the time (in milliseconds) between heartbeat messages.
- Activation Interval (ms) Secondary process engines track heartbeat messages from the master engine. This field specifies the amount of time since the last heartbeat from the master that before the secondary restarts the process starters and process instances.
- Preperation interval (ms)(Actibation delay) When a master engine resumes operation, the secondary engine shuts down and returns to standby mode. For some situations, it may be necessary to ensure that the secondary engine has completely shut down before the master engine resumes operation. Default is zero.
These properties correspond to :
Engine.FT.HeartbeatInterval = 8000
Engine.FT.ActivationInterval = 25000
Engine.FT.ActivationDelay = 18000
You might want to double the values if you wish.
Hopefully this should address the problem.
Here are the reasons you might see duplicate durables:
1) This Could be happening because there is a JMS Queue Subscriber and JMS Topic Durable Subscriber in one engine and both are using same JMS Connection - this is a know issue (Defect ID 1-6X3LX1) - please >> make sure that they both uses their own JMS Connection and in Advanced tab take out the appropriate Connection Factory.
2) Use Client ID if you haven't already - The Client ID is set in the 'JMS Connection' palette.
The durable subscription name that is created in TIBCO EMS has the following format:
<Client ID>:<Durable Subscription>
If the Client ID is left blank, BW drives a name based on the 'JMS Connection' name and the 'BW project' name. This drived name is used as a Client ID and has the following structure 'BW-<JMS Connection name in BW>-<BW Project Name>'
3) We have seen a case while primary engine is going down, the stand by engine will get activate; as the results, duplicate durables get created. To ensure the primary engine shutdown completely, please add the following properties to your deployed TRA file:
- Heartbeat Interval (ms) The master engine of a fault-tolerant group broadcasts heartbeat messages to inform the other group members that it is still active. The heartbeat interval determines the time (in milliseconds) between heartbeat messages.
- Activation Interval (ms) Secondary process engines track heartbeat messages from the master engine. This field specifies the amount of time since the last heartbeat from the master that before the secondary restarts the process starters and process instances.
- Preperation interval (ms)(Actibation delay) When a master engine resumes operation, the secondary engine shuts down and returns to standby mode. For some situations, it may be necessary to ensure that the secondary engine has completely shut down before the master engine resumes operation. Default is zero.
These properties correspond to :
Engine.FT.HeartbeatInterval = 8000
Engine.FT.ActivationInterval = 25000
Engine.FT.ActivationDelay = 18000
You might want to double the values if you wish.
Hopefully this should address the problem.
Issue/Introduction
Why do we sometimes see duplicate Durables when running BW from Admin?
Feedback
Yes
No
Powered by
