UIMA AS client not handling GetMeta Ping timeout correctly

The uima-as client marks a service as unavailable when it detects a timeout on a CAS. A subsequent CAS (submitted by an application) is be added to a Pending Dispatch list and the uima-as client sends a GetMeta ping request to a service to check if it is alive. While the client awaits response, any additional CAS submitted by an application is added to the Pending Dispatch List. When the service responds to the GetMeta ping all CASes from a Pending Dispatch list are dispatched to the service. When the service does not respond to the GetMeta ping, the uima-as client fails to reject CASes sitting in the Pending Dispatch list. This may cause a hang if the application draws CASes from a Cas Pool. The client should throw a timeout exception on all CASes in the PendingDispatch list on GetMeta ping timeout