Why does an RTclient receive a monitor result message for another client in a different project?
Article ID: KB0090793
Updated On:
| Products | Versions |
|---|---|
| TIBCO SmartSockets | - |
| Not Applicable | - |
Description
Resolution:
If two RTclients issue a client_names watch and both are connected to an RTserver cloud under separate projects but with the same unique_subjects, then one RTclient will receive watch result messages intended for the other monitoring client. This is reproducible with two RTservers, but not with one. This is a known issue. As of SmartSOckets release 6.8 CFIX_V2 the work around is to NOT set the unique_subject of the monitoring clients or to make sure that the unique_subjects of the clients (if set) are unique across all projects.
If two RTclients issue a client_names watch and both are connected to an RTserver cloud under separate projects but with the same unique_subjects, then one RTclient will receive watch result messages intended for the other monitoring client. This is reproducible with two RTservers, but not with one. This is a known issue. As of SmartSOckets release 6.8 CFIX_V2 the work around is to NOT set the unique_subject of the monitoring clients or to make sure that the unique_subjects of the clients (if set) are unique across all projects.
Issue/Introduction
Why does an RTclient receive a monitor result message for another client in a different project?
Feedback
Yes
No
Powered by
