Another one related to issues I've mentioned in other recent posts:
I'm doing some debugging related to undesired side effects in one of our applications after it gets a "Failed to connect (reconnect disabled)" error while sending to or receiving from the C++ broker. In then "manually" reopens the connection after a slight delay. As parts of the reconnect logic, I also tend to get "'session-busy: Session detached by peer'". This is possibly triggered by the connect itself, but it could also come from other operations done just after connecting.
This would be a whole lot easier if I could provoke the errors into occurring, so as to speak. I guess the "failed to connect" error means the broker has dropped the connection, but is there a way I can force it to do that (without restarting)? And how about the "Session detached by peer"? It's not clear to me when exactly I get that, but I guess it's related to sessions that existed before the connection was closed. Which (according to information I got here earlier) Connection::open() might try to recreate, but perhaps the operation fails? Can I somehow manipulate the state so I can find out more about the behaviour?
Thanks. - Toralf --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
