How important is it to keep the system clocks synchronized among server instances hosting distributed destination members and their connection factories?
A. It is very important when using distributed topics with non-durable subscribers. This is because if the clocks between the servers become too far askew, there is a possibility that messages will not be delivered. Here’s how this could happen: both the connection factory for the distributed topic and the distributed topic members will use their local system clock to see if a consumer is created after a message is published. Messages published to topics before consumers are created are not visible to consumers. There is always a race in any topic when the message is published before the consumer is created. Distributed topics widen this race when the system clocks on the server instances hosting the connection factory or the distributed topic members are not in sync. For example, if your application creates short-lived, non-durable topic consumers, and a consumer is listening through a connection factory on ServerA, but the message is published to distributed topic member on ServerB,
Related Questions
- How important is it to keep the system clocks synchronized among server instances hosting distributed destination members and their connection factories?
- I have several websites on the Host@Freeparking shared hosting system, how do I move these onto my managed dedicated server?
- How To Find Virtual Server Hosting System Deals?
