Ticket Navigation

Ticket #98 (closed defect: duplicate)

Opened 1 year ago

Last modified 1 year ago

JMS Notification Message Ordering Not Guaranteed

Reported by:	mroy	Assigned to:	mroy
Priority:	major	Milestone:	3.0 milestone2
Component:	openanzo-repository	Version:	3.0
Keywords:	jms notification	Cc:

Description

JMS and thus ActiveMQ only guarantee that messages are ordered per consumer object on the client. Since our notification system is based on having 1 consumer object per tracker, and then 1 consumer object for the overall transaction start and stop events, we can't guarantee that we get the messages that make up a transaction before we get the transaction end event. This leads to some of the problems we have now where notification test fail, and after investigation, one of the causes is that transactions are considered complete, even before all their contents are received. In order to solve this for the design we have, it is felt that we need to do our own message selector registration and filtering on the server, and leave the client with only 1 consumer object, thus preserving order. Since we can have more than one server processing update messages for clients, we also need to update the notification proxy layer in order to allow out of order transaction events to be inserted into the proxy in the right location.

Change History

Download in other formats:

The Open Anzo Project

Semantic Application Middleware