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]
