Investigate the AMQP deserialisation logic to see what happens when field-values are repeated.
Quoting on #development channel:
"we receive a message on the wire that maps to class Foo(val a: String, val b: String). but the on-wire representation is something like a: "Foo" b: "Bar" a: "Baz" - what happens?"
Understand what the existing behaviour is - is this classed as message corruption or does the duplicate field value parsed & accepted?
Does this match up with what the expected behaviour is?
Add any necessary test cases to cover this scenario