We have a consumer program (UPA) that subscribes to Source Directory information as well as making individual item subscriptions.
Current functionality is to set status for all items to Stale when receiving a Source Directory Update for the relevant service saying that service is DOWN.
Items status is returned to OK again when receiving a REFRESH message with that status, but we have seen that those are not always received.
Is it correct to assume that receipt of any RSSL_MC_UPDATE type message for an item means that status is now OK?
This problem is only occurring for a specific type of failure/recovery scenario where an ADH is restarted (fails over to buddy). In that case, on our TREP we see extra Source Directory messages approx. one minute after the initial failure/recovery which inform us that the service is down, even though it really isn't. Can you explain this behaviour on TREP and advise on how it might be remedied?