1.

What Are The Different Delivery Modes Available In Ems?

Answer»

Persistent:

When a producer sends a PERSISTENT message, the producer must wait for the server to reply with a confirmation. The message is persisted on disk by the server. This DELIVERY mode ensures delivery of messages to the destination on the server in almost all circumstances. However, the cost is that this delivery mode incurs two-way network traffic for each message or committed transaction of a group of messages

Non-Persistent:

  • Sending a NON_PERSISTENT message omits the overhead of persisting the message on disk to improve performance.
  • If authorization is disabled on the server, the server does not send a confirmation to the message producer.
  • If authorization is enabled on the server, the DEFAULT CONDITION is for the producer to wait for the server to reply with a confirmation in the same manner as when using PERSISTENT mode.
  • Regardless of whether authorization is enabled or disabled, you can use the npsend_check_mode parameter in the tibemsd.conf file to specify the conditions under which the server is to send confirmation of NON_PERSISTENT messages to the producer.

Reliable:

  • EMS extends the JMS delivery modes to include reliable delivery. Sending a RELIABLE_DELIVERY message omits the server confirmation to improve performance regardless of the authorization setting.
  • When using RELIABLE_DELIVERY mode, the server never sends the producer a receipt confirmation or access denial and the producer does not wait for it. Reliable mode decreases the VOLUME of message traffic, ALLOWING higher message rates, which is useful for messages containing time-dependent data, such as stock price quotations.

Persistent:

When a producer sends a PERSISTENT message, the producer must wait for the server to reply with a confirmation. The message is persisted on disk by the server. This delivery mode ensures delivery of messages to the destination on the server in almost all circumstances. However, the cost is that this delivery mode incurs two-way network traffic for each message or committed transaction of a group of messages

Non-Persistent:

Reliable:



Discussion

No Comment Found