When client received incorrect byte array of PdxType due to broken socket, it should be retried

Client's query for PdxType will get a byte array in response message. The byte array is the same at the server, but different query from different client might receive wrong byte array and end up with PdxSerializationException in scalability test with server HA. This could caused by socket broken and bytes are not flushed. We expected such broken socket scenario and prepared some retry lock. However, our retry logic did not consider above scenario, i.e. the message header is correct, but the embedded byte array for PdxType is wrong.

The solution is to retry in this case.