An easy thing to try would be to turn on protocol logging. In qpidd.conf file or on the command line add
--log-enable trace+:Protocol This would expose what led up to the session being rejected. The protocol logs will show if the broker is spontaneously closing the session or if the client(s) are violating AMQP rules in some way. Dropping connections or resetting sessions from within the broker would be really hard. Testing has focused on having cruel clients who close connections and sessions at inopportune moments to test that the broker survives. -Chuck ----- Original Message ----- > From: "Toralf Lund" <[email protected]> > To: [email protected] > Sent: Friday, March 29, 2019 8:26:21 AM > Subject: Force (C++) broker to drop connection and/or reset session > > 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: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
