Description of problem: The following JMS client behavior change puts the supported clients out of sync: please see bug 962347. Per discussion with Rajith, this change was made on purpose (to ensure users don't create durable temp queues) and the check is very useful. I'm filling this bz to let the developers consider whether this change shall be also reflected by other supported clients. If the check is going to be implemented in the c++ client as well, the issue shall be also cloned for python client. Version-Release number of selected component (if applicable): qpid-cpp-*-0.22-2 qpid-java-*-0.22-2 How reproducible: 100% Steps to Reproduce: 1. Use the following address string for receiver: "amq.topic/some_subject;{ link: { durable: true } }" 2. Exception when using JMS client, no exception using c++ client (durable subscription queue created) Actual results: Different behavior of supported clients Expected results: Supported clients behaves the same way Additional info: