Major Description
There is an issue with the processing of the new BrokerSubscriptionInfo command that is used for sync durables over a network bridge that can cause the brokers to get stuck starting up. Depending on the timing of the BrokerSubscriptionInfo being sent, each broker can get stuck waiting to finish creating static destinations and not be able to finish because it's waiting for the other broker to respond. The root of the problem is the new countDown latch that was added when processing the new BrokerSubscriptionInfo object. The fix for this to prevent a deadlock is to move that processing into a new thread so the transport doesn't get blocked and can continue to process other commands.