# Non blocking check for WS

**URL:** <https://community.gatling.io/t/non-blocking-check-for-ws/6239>\
**Category:** Gatling (Open-Source)\
**Created:** [September 6, 2021, 1:25pm UTC](https://community.gatling.io/t/non-blocking-check-for-ws/6239 "2021-09-06T13:25:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sgt](https://avatars.discourse-cdn.com/v4/letter/s/df705f/32.png) [@sgt](https://community.gatling.io/u/sgt)\
**Post date:** [September 6, 2021, 1:25pm UTC](https://community.gatling.io/t/non-blocking-check-for-ws/6239/1 "2021-09-06T13:25:42Z")

</div>

Hi,

does anyone knows how to do a non-blocking check for a websocket? It used to be known as wsListen in Galing 2… versions. From version 3 it seems that we only have blocking await check.

I can’t use await before a HTTP request is executed and I can’t use await after HTTP response is received because messages come inside the HTTP’s responce. So the only option would be to make a non-blocking check before the request is sent.

Regards

---

<div class="post-metadata">

**Author:** ![slandelle](https://dub1.discourse-cdn.com/flex013/user_avatar/community.gatling.io/slandelle/32/4_2.png) [@slandelle](https://community.gatling.io/u/slandelle)\
**Post date:** [September 7, 2021, 11:32am UTC](https://community.gatling.io/t/non-blocking-check-for-ws/6239/2 "2021-09-07T11:32:08Z")

</div>

Hi,

The implementation in Gatling 2 was very buggy as this use case is very hard to implement.  
It hasn’t been implemented in Gatling 3 yet.

If you’re really in dire need of this feature, you can either contribute it, or contract with us so we can allot resources to work on it.

Regards,