You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 6, 2021. It is now read-only.
I'm running a Jersey/Spring based API on Tomcat 8 that uses the deepstream Java client to connect to deepstream and then send various RPC requests. I've been developing and testing on Windows and everything has been fine.
Now I'm moving it into production on AWS (latest Linux on a t2.small). If I stop the deepstream server, the CPU immediately goes to 100% for the Tomcat process. When I restart deepstream and the API logs back in to deepstream but the CPU still remains at 100%. Only a Tomcat restart fixes it.
I'm also using the client in Android and it has the same issue. Though CPU goes from 5% to 60%
The text was updated successfully, but these errors were encountered:
We just saw the same issue on our java clients when restarting aws ds servers.
Even with 'wrapped' re-connection logic (full client.close(), client=null, client=new DeepstreamClient, client.login) - no recovery, our service nodes need full restarts.
It wasn't the change from Windows to Linux. It was the change from ws to wss. Seems there may be an infinite loop issue with the underlying Java-Websocket.
Thanks for raising, we'll need to get a release date for java websocket
1.3.5 asap. A temporary workaround for backend services could be switching
back to ws and using e.g. https://www.stunnel.org/index.html for encryption
I'm running a Jersey/Spring based API on Tomcat 8 that uses the deepstream Java client to connect to deepstream and then send various RPC requests. I've been developing and testing on Windows and everything has been fine.
Now I'm moving it into production on AWS (latest Linux on a t2.small). If I stop the deepstream server, the CPU immediately goes to 100% for the Tomcat process. When I restart deepstream and the API logs back in to deepstream but the CPU still remains at 100%. Only a Tomcat restart fixes it.
I'm also using the client in Android and it has the same issue. Though CPU goes from 5% to 60%
The text was updated successfully, but these errors were encountered: