SQS - Interrupting long-polling

[upsidedownsmile]

According to #655 the only way to interrupt receiveMessage call is by shutting down the client. I've been testing this and I found a problem, in the SQS side the connection will still be "alive" and the next message will be sent through it. For example, if using an AsyncHandler this will trigger the onError method. But no matter how you are receiving messages, the message needs to wait for the visibility timeout to be resent to another subscriber.
I also found this comment that complains about the same thing.

[varunnvs92]

The issue is same as the one reported in aws-sdk-java-v2 repo. Closing this and track it aws-sdk-java-v2 repo
aws/aws-sdk-java-v2#1395