This largely depends on the protocol that underlies the jdbc connection. Typically this is socket based so the tcp/ip keep alive settings can be used such that that aborted client socket is visible to MySQL a little earlier.
The problem with an abortive shutdown is that the broker jdbc connection will not be closed, so it is up to some layer to determine that the underlying connection is stale.
Thanks for your reply. Using TCP keep alive helps with a fast fail over. Although, I am seeing quite a few issues now.
The master will never start again. The logs would be empty despite changing to DEBUG in log4j
The slave that became a master is not capable of inserting messages to the database due to Duplicate entries for Key 1.
Is this the right place to discuss these issues? Since, I am entirely new to this stack, has anyone performed & documented failover tests on Fuse Broker?