Description of problem: If clients run in synchronous durable mode (AMQP 1.0 java client for example), performance can suffer due to long (500 ms) timeout. (See BZ 1087828) We propose adding a broker configuration setting so the user can control this timeout. This may not completely solve the problem, but it will allow some tuning to lessen the problem and will allow for some testing that could be helpful to understanding the issue. Version-Release number of selected component (if applicable): qpid-cpp-0.34-3 How reproducible: Steps to Reproduce: (See BZ 1087828) Actual results: Synchronous durable messaging is very slow (rate can be as slow as 1 per second). Expected results: Lower the timeout and see that the java client performs better for synchronous durable messaging. Additional info: