What I get from this is that the C++ client gives up retrying when it gets a 320 (connection forced) reply from the broker.
As Keith mentioned earlier, the error message is basically saying "Yes, the broker is up... but it isn't fully configured yet", and the 320 error code (as defined by the AMQP 0-10 spec) says "The client may retry at some later date."... so if the C++ client would continue retrying on receipt of this error then you would establish a connection. I guess this would require a C++ client change, but Gordon would be the one to know here... -- Rob On 20 January 2016 at 10:08, [email protected] <[email protected]> wrote: > Ok, I was able to produce a protocol trace with trace+ > The situation is as follows: > First the client is started. The broker is not active and thus the client > is > trying to reconnect. > Then, after a while, I start the broker. When the broker is almost booted > completely, the client receives the corresponding exception. > > Here is the trace: > protocolTrace.txt > <http://qpid.2158936.n2.nabble.com/file/n7636879/protocolTrace.txt> > > > > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/Several-issues-with-the-Java-Broker-tp7636726p7636879.html > Sent from the Apache Qpid users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
