Connections pending during the reconnection process.

This problem occurs with multiple clients in the same JVM. When the broker is restarted, the first client reconnects normally, while nextclients initiate the TCP connection but never send the expected CONNECT frame.
This behavior can be observed in the Wireshark capture below. The TCP connection is established (packets 4445, 4449, and 4452), and then, 15 seconds later, the connection is closed by the broker. Increasing the broker'stimeout does not change this behavior.

Reproduce the broker-restart scenario with multiple clients in the same JVM and compare the Wireshark capture with the client’s reconnection path. Investigate why later TCP connections do not send CONNECT; the issue is done when all clients reconnect successfully after the broker restarts.

Written by the indexing model from the issue text.