Description of problem: UnknownMethod error is returned when connection/session qmf methods are called on amqp1.0 objects. Calling these methods on amqp0-10 connection/session objects works as expected. Calling the above methods using amqp1.0 do not solve the issue: ./qmf2_qpid_ctrl --connection-options "{protocol:amqp1.0}" -c connection -i qpid.10.34.33.110:5672-10.34.33.110:42672 close {'_values': {'error_code': 2, 'error_text': 'UnknownMethod'}} feel free to change the component to qpid-cpp if appropriate Version-Release number of selected component (if applicable): qpid-qmf-0.22-25.el6 python-qpid-qmf-0.22-25.el6 qpid-cpp-*-0.22-30.el6 How reproducible: 100% Steps to Reproduce: 1. ./drain -f --connection-options "{protocol:amqp1.0}" 1. qpid-tool 2. call <connection-id> close 3. qpid: UnknownMethod (2) - {} Actual results: UnknownMethod error returned on amqp1.0 connection/session qmf methods calls Expected results: qmf method successfully executed Additional info:
"Steps to Reproduce" correction: - 1. ./drain -f --connection-options "{protocol:amqp1.0}" - 1. qpid-tool - 2. call <connection-id> close - 3. qpid: UnknownMethod (2) - {} + 1. ./drain -f --connection-options "{protocol:amqp1.0}" amq.direct & + 2. qpid-tool + 3. call <connection-id> close + 4. qpid: UnknownMethod (2) - {}
Fixed upstream: https://svn.apache.org/r1560393
Fixed: Method calls on amqp1.0 objects works the same way as on 0-10 object: - connection close() method works as expected - session dettach() method works as expected - session methods: resetLifespan(), solicitAck(), close() are not implemented (tracked via Bug 1049514)
This issue has been fixed. Verified on rhel6.5 (x86_64, i386). packages under test: qpid-cpp-*-0.22-37 -> VERIFIED