How is Gmd_Publish_Timeout used?
Article ID: KB0085518
Updated On:
| Products | Versions |
|---|---|
| TIBCO SmartSockets | - |
| Not Applicable | - |
Description
Resolution:
When an RTclient first publishes a message that uses either GMD or Load Balancing the publishing RTserver must collect information from all the other RTservers about the clients subscribed to the subject the message is published to. It then builds the internal structures needed. If no other GMD/LB message is published in Gmd_Publish_Timeout amount of time (300 seconds by default) then the RTserver removes the internal structures it has created. By setting this option to 0 the RTserver will no longer; check for the frequency of GMD/LB publishing, use cycles building up and tearing down its internal structures, or printing error messages to the RTserver log files. The amount of memory used by the RTserver to maintain these data structures is, 4 bytes per client subscribed per subject, sounder normal circumstances there is not a significant memory savings by destroying them.
When an RTclient first publishes a message that uses either GMD or Load Balancing the publishing RTserver must collect information from all the other RTservers about the clients subscribed to the subject the message is published to. It then builds the internal structures needed. If no other GMD/LB message is published in Gmd_Publish_Timeout amount of time (300 seconds by default) then the RTserver removes the internal structures it has created. By setting this option to 0 the RTserver will no longer; check for the frequency of GMD/LB publishing, use cycles building up and tearing down its internal structures, or printing error messages to the RTserver log files. The amount of memory used by the RTserver to maintain these data structures is, 4 bytes per client subscribed per subject, sounder normal circumstances there is not a significant memory savings by destroying them.
Issue/Introduction
How is Gmd_Publish_Timeout used?
Feedback
Yes
No
Powered by
