In a cluster configuration, JMS queues are associated with one member of the server cluster and access to the queues is provided by the Java Naming and Directory Interface (JNDI) service.
The JDNI service is available across all the members on the cluster.
All cluster members can produce messages into the sequential queue. A single-threaded cron task reads the messages in the sequenetial queue to support first-in-first-out processing.
The continuous queue is multi-threaded on the consumer side to support message processing in high volumes. In this queue, the message processing order is not considered.
Enterprise service messages that use the sequential queue are processed in a strict sequential order. Message processing is single-threaded. Clustering does not significantly impact the processing performance of messages through the sequential queue.