UIMA AS client fails when service broker is restarted

If an application creates multiple instances of UIMA AS client, each connected to a different service, a broker restart is not handled correctly.Only one instance of a client re-initializes correctly and handles the re-connect. Remaining client instances still use stale broker connection. When a connection failure is detected, the client code enters a loop trying to recover the connection. Once recovered, a singleton SharedConnection object is initialized with a new Connection, message listeners of all clients are restarted on new temp reply queues but MessageProducers are not re-initialized. Modify code that detects connection failure to invalidate MessageProducer in each client. Also, add code to detect invalid MessageProducer and force creation of a new instance using new Connection object.