Hey James,
I've captured the details here
http://issues.apache.org/activemq/browse/AMQCPP-157
Looks like the C++ producer's response correlator timed out when
waiting for a response for a sent bytes message (this timeout defaults
to 3 seconds).
It may simply be that the app was bogging down the machine (win32) and
the default timeout wasn't sufficient.
Is there a flow control that gets imposed on producers that are
flooding the broker with messages? If so, could you point me to where
this is done in the Java client? It may be that we already have this
flow control implemented - I know Tim has been working on
compatibility with the 5.0.0 broker.
Thanks,
Nate
On Dec 17, 2007, at 6:01 AM, James Strachan wrote:
On 17/12/2007, Hellweek <[EMAIL PROTECTED]> wrote:
When performing the test with C# consumers the CPP producers fail.
The CPP consumers do not fail with C# producers.
Ah great, thanks. This has been a long thread, forgive me if you've
already answered this but how do they fail? Do they core dump? Getting
the stack trace could help.
Am wondering if its the new producer flow control messages that are
not being handled by CPP?
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://open.iona.com
