The client doesn't disconnect the TCP connection on closure after receiving an AMQP Close frame, so if the other side doesn't either it will remain open. This is true of local and remote initiated closures. For remote closures, the client should additionally 'respond' first by sending its own Close frame as the protocol is symmetric and peers may or may not wait for the matched frame.
The client doesn't disconnect the TCP connection on closure after receiving an AMQP Close frame, so if the other side doesn't either it will remain open. This is true of local and remote initiated closures. For remote closures, the client should additionally 'respond' first by sending its own Close frame as the protocol is symmetric and peers may or may not wait for the matched frame.