Well, not sure. I would review the test case to make sure it's set up exactly the way you guys have it. The goal is to get the test case to lock up somehow so that it doesn't reach "making progress 99"
Or you could take some time-series (3-4 snapshots) of the broker's threads (both brokers) so that we can see the progression of the threads over time to see what they're doing. On Fri, Sep 27, 2013 at 11:28 AM, someword <derek.ol...@jivesoftware.com>wrote: > Blarhg! My prior post was out of order. > > Thanks! > The updated test runs to completion > > I do see this which happened last time to (just this one occurrence during > the test run) > > making progress 0 > You had an issue sending back messages! > making progress 1 > > The test run summary looks clean though > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 55.081 sec > > At this point is it fair to say that the symptoms we are seeing are not > related to activemq blocking the producer but one or all of the ruby stomp > gem, ssl and or ruby itself? > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Did-I-turn-off-producer-flow-control-correctly-tp4671619p4671919.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
