Hi, Someone I'm working with ran into the bug listed in:
https://issues.apache.org/activemq/browse/AMQCPP-171 which where code was timing out because of a slow connection. That issue was resolved by setting the property transport.ResponseCorrelator.maxResponseWaitTime to something higher. The code we're using is old (2.1RC3), and we're going to upgrade to 2.2.1. I looked at the configuration page (http://activemq.apache.org/cms/configuring.html) and saw this note next to the property Milliseconds to wait for responses from the broker. (Removed as of ActiveMQ-CPP 2.2.1) Is this a non-issue because of changes in 2.2.1, or is there a different configuration option that's available? We're in the process of upgrading our code base, and I'd like to set that maxResponseWaitTime higher, if it's still necessary to do so. Thanks, Steve -- View this message in context: http://www.nabble.com/maxResponseWaitTime-removed--tp19611709p19611709.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
