Errata

Enterprise Messaging

Errata for Enterprise Messaging

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted by Date submitted
Other Digital Version DUPS_OK section

If like the author said, the message in dups_ok mode was automatically marked as delivered, acknowledged and then removed in JMS provider. How's it possible for there to be a duplicate message. The message is GONE!!!. How can the JMS provider to deliver it again? I read the comment at

http://docs.oracle.com/cd/E19587-01/821-0029/aeqbk/index.html

and come with an answer I think it is better. The JMS provider doesn't acknowledged and removed the message. The consumer instead of immediately acknowledging the message, It does it in a batch so that the communication between JMS provider and client become less chatty. Because the acknowledgement is done in a fixed interval, there is a chance that the JMS failed and after a restart, it sends out a DUPLICATE.

Anonymous  Jun 07, 2015