AMQP RPC client doesn't respect correlation IDs
Reported by John Wright | February 21st, 2011 @ 12:38 PM | in 0.9.3
The AmqpRpcClient currently doesn't check whether the reply it receives has a correlation ID that corresponds to the request's message ID. This means that requests and replies can be jumbled up, breaking Diffa's internal processing.
Comments and changes to this ticket
-
John Wright February 21st, 2011 @ 12:59 PM
- State changed from “open” to “resolved”
- Assigned user changed from “John Wright” to “Paul Jones”
Fix pushed to branch 191 at git://github.com/johnwright/diffa.git
-
Paul Jones February 21st, 2011 @ 03:27 PM
- State changed from “resolved” to “open”
QA remarks:
- This is something a test could be quite valuable for, since it was a difficult behaviour to diagnose in a real environment. I'm just not sure how hard building the test framework to reproduce it would be.
- I've extracted the case object change and attached it to #190.
-
Paul Jones February 22nd, 2011 @ 07:57 AM
- Assigned user changed from “Paul Jones” to “John Wright”
-
John Wright February 23rd, 2011 @ 11:38 AM
- State changed from “open” to “resolved”
- Assigned user changed from “John Wright” to “Paul Jones”
Added a unit test to verify that the correlation ID checking is really happening.
-
-
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A Real Time Differencing Tool.
People watching this ticket
Paul Jones
Referenced by
-
191
AMQP RPC client doesn't respect correlation IDs
(from [8b2ef8cf0e9ef161e5eed72077b78a62e1730e51])
Merge [...