Ticket #83 (assigned defect)

Opened 2 years ago

Last modified 2 years ago

when async reliable message over http then processing of response ack can be earlier than processing of user message

Reported by: sacha Assigned to: sacha (accepted)
Priority: major Milestone: basic-messaging
Component: message-service-handler Version: pre-first-version
Keywords: Cc:

Description

when exchanging 80+ messages between two systems in the same HefeWeizen (high load of the system) the following problem can occur:

a side: tasker 1 user message is sent over http. a side: tasker X to wake up in x time b side processes incoming user message and creates and sends ack a side: receives ack and sets status of message to sent (no state machine of message causes it to let the new state be set) a side tasker 1 confirms that the message was technically sent. this overwrites the previous state to "technically sent". a side the tasker X wakes up and sees that the message is not in a final state and causes a resend of the user message

Change History

02/25/07 13:08:28 changed by sacha

  • status changed from new to assigned.