Resolution:
Problem Description:

A monitoring client which is watching client names to discover new clients joining the application then sends a client_general_poll_call (or other poll request) to the new client, but occasionally the monitoring client does not receive a poll_result message back.

Environment:

All

Symptoms:

Missing poll_result messages

Cause:

When watching client_names the RTserver may send the mon_client_names_status message before the newly connected client has fully subscribed to it's own unique_subject.  If a poll_call is sent to the new client before the unique_subject has been subscribed to then the poll_call will be silently ignored.    

Resolution:

The monitoring application should include logic to manage this potential race situation.  Either it can include a small (~0.1 sec) fixed delay before sending the poll_call to a new client, or it should maintain it's own internal list of which clients it has sent a poll request to but has not yet received a reply from, and then periodically resend the poll request to any outstanding clients.

A monitoring application randomly does not receive a mon_client_general_poll_result back from a client.