On 01/07/2015 03:44 AM, Rafael Schloming wrote:
On Tue, Jan 6, 2015 at 3:36 PM, Gordon Sim <[email protected]> wrote:
On 01/06/2015 07:39 PM, Rafael Schloming wrote:
Hey, I made a bunch of updates to them, can you do a pull and see if this
is still an issue?
That seems to fix it.
Actually, it turns out the hang is caused by another process listening
on port 5672. It was simply coincidence that I did not have a broker
running when I retested.
(A separate issue I just discovered by accident is
that python-test seems to hang if PN_TRACE_FRM is set to 1).
I think that's because there are several tests that transfer enough
messages to exceed the default session window. The tracing slows them down
enough that the tests take a really really long time. I don't know if they
actually hang or not, but they probably appear to.
I'm pretty sure in my case its a hang as there is no cpu activity at all.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
