It has assumptions based on 0-10 (and a particular pattern for 0-10 at that) built into the underlying transport code (which should be protocol agnostic).
As AMQP 1.0 makes it much simpler and more likely for less synchronous handshaking, the '3 reads' magic doesn't work and causes 1.0 connections to be terminated incorrectly. Either the original solution needs to be reimplemented or it needs to be possible to disable it for use with 1.0.
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Fix Version/s||0.23 [ 12324273 ]|
|Fix Version/s||Future [ 12315490 ]|
|Resolution||Fixed [ 1 ]|
|Field||Original Value||New Value|
|Summary||max-negotiate-time feature breaks AMQP 1.0||max-negotiate-time feature breaks AMQP 1.0 (and arguably doesn't achieve the desired objective anyway)|