# solace websocket connection interrupted - Messages sometimes doesn´t reach the end client

**URL:** <https://community.solace.com/t/solace-websocket-connection-interrupted-messages-sometimes-doesn-t-reach-the-end-client/1896>\
**Category:** Training, Tips and Tricks\
**Created:** [April 4, 2024, 7:17am UTC](https://community.solace.com/t/solace-websocket-connection-interrupted-messages-sometimes-doesn-t-reach-the-end-client/1896 "2024-04-04T07:17:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Misk](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/misk/32/507_2.png) [@Misk](https://community.solace.com/u/Misk)\
**Post date:** [April 4, 2024, 7:17am UTC](https://community.solace.com/t/solace-websocket-connection-interrupted-messages-sometimes-doesn-t-reach-the-end-client/1896/1 "2024-04-04T07:17:01Z")

</div>

**solace websocket connection interrupted - Messages sometimes doesn´t reach the end client**  
We seeing some issues, that the websocket was not disconnected and died, but that it was the same, with the same solclient id before and after, when it happened. Like there was a hitch just in communication.  
"  
with the websocket subscriptions. The clients (browser) subscribes to certain topics. During a session they can retrieve some messages on that topic, but sometimes they receive nothing. Its totally random. We can see from our backend services that they are atleast published ok.  
"  
so the question is if it is solace, network or the client?  
we now trying to increase the:  
Web Transport  
Inactive Timeout : 30 seconds \> 100 seconds, for notice if any changes in behaviour.  
(cause on some thread its pointing out that it could help above 75 s)

Any thoughts from anyone?

---

<div class="post-metadata">

**Author:** ![Aaron](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/aaron/32/843_2.png) [@Aaron](https://community.solace.com/u/Aaron)\
**Post date:** [April 8, 2024, 5:13am UTC](https://community.solace.com/t/solace-websocket-connection-interrupted-messages-sometimes-doesn-t-reach-the-end-client/1896/2 "2024-04-08T05:13:26Z")

</div>

Is this a browser application? Is this using MQTT API or Solace native JS API? Is there any logging on client-side to indicate issue? e.g. timeout. Is there any entries in broker’s `event.log` to indicate issue? e.g. “force disconnect due to keepalive”.