Thanks for closing the loop on this!
On Wed, Dec 12, 2012 at 3:50 PM, Steve.V. <stephen.vinc...@sas.com> wrote: > I looked deeper into "MessageServlet.java" and see the getReadTimeout > changes > readTimeout values that are less than zero or greater than > maximumReadTimeout to maximumReadTimeout. That explains why I was seeing a > 20 second timeout. In my client application, I plan to set a default > time-out value of 1 millisecond since I think it will be more common for my > users to expect an immediate response when the destination has no messages. > > > > ----- > Stephen Vincent > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/I-see-defaultReadTimeout-1-in-MessageServlet-java-but-experience-20-secs-tp4660427p4660571.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta