SSL NetworkConnector Blocks Shutdown when Both Sides of Network Failover Simultaneously

(Work in Progress) Set up two brokers with tcp+ssl transports for broker to broker connections, JDBC persistence adapters and each with their own schema in the database Clients are XA-transacted MDBs running in JBoss EAP (A servlet is used to produce a message load) Set up a load in both directions by producing and consuming from the same queue on both sides of the NOB. While production is in-progress, stop the RDBMS to force locker failures on both sides of the NOB at once. Sample Transport and NOB config: <sslContext> <sslContext keyStore= "/opt/app/SSL/test.keystore" keyStorePassword= "${keystore.password}" trustStore= "/opt/app/SSL/cacerts.jks" trustStorePassword= "${truststore.password}" /> </sslContext> <transportConnectors> <transportConnector name= "nio+ssl" uri= "nio+ssl://0.0.0.0:61617?transport.enabledProtocols=TLSv1.2&amp;maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600" /> <transportConnector name= "ssl2" uri= "ssl://0.0.0.0:61618?transport.enabledProtocols=TLSv1.2&amp;maximumConnections=200&amp;wireFormat.maxFrameSize=104857600&amp;transport.soTimeout=60000&amp;transport.soLinger=0" /> </transportConnectors> <networkConnectors> <networkConnector name= "NETWORK_TO_PAIR_2" uri= "masterslave:(ssl://amq03.example.com:61618?soWriteTimeout=20000,ssl://amq04.example.com:61618?soWriteTimeout=20000)" networkTTL= "2" conduitSubscriptions= "false" suppressDuplicateQueueSubscriptions= "true" userName= "BrokerGroup" password= "${brokernetworking.password}" /> </networkConnectors>