Description of problem:

As a result of bug 812376, the 0-10 client reports following exception when trying to produce/consume message with routing key longer than 255 characters:
illegal-argument: Value for routingKey is too large

This limitation does not applies for 1.0 clients, ie. producing/consuming using routing key longer than 255 characters works well.

When 0-10 receiver is consuming messages and a message with routing key longer than 255 characters is sent to the consumer using 1.0 producer, the consumer ends with an exception.

So it is possible to send a message using 1.0 producer that forces the 0-10 consumers to disconnect (although with proper exception).

I am not claiming that this behavior is necessary wrong, the proper exception is reported. I am raising the bug in order to let the team thing about the correct behavior here. If this would be identified as correct behavior it should be at least documented. In this case please change the component to doc.

Notes:
When ignoring the exception on the client side, next fetch command gets again the same message and ends in a loop.
Reconnect won't help in this case

Version-Release number of selected component (if applicable):
qpid-cpp-*-0.22-14

How reproducible:
100%

Steps to Reproduce:
1. ./drain amq.topic/a.* -f
2. ./spout --connection-options {protocol:amqp1.0}  "amq.topic/a.AReallyLongSubjectAReallyLongSubjectAReallyLongSubjectAReallyLongSubjectAReallyLongSubjectAReallyLongSubjectAReallyLongSubjectAReallyLongSubjectAReallyLongSubjectAReallyLongSubjectAReallyLongSubjectAReallyLongSubjectAReallyLongSubjectAReallyLongSubjectAReallyLongSubject"
3. subscription ends with following exception:
illegal-argument: Value for routingKey is too large

Actual results:
amqp0-10 clients ends with exception on receiving a message with routing key longer than 255 characters.

Expected results:
not sure

Additional info: