On Fri, Mar 1, 2019 at 4:46 AM Mark Thomas <ma...@apache.org> wrote: > > On 28/02/2019 20:29, Austin Bookhart wrote: > > Hi, > > > > I have a question regarding an asynchronous websocket implementation > > we have in our application. We have run into issues where on a rare > > occasion the websocket endpoint will become unusable due to what seems > > to be a thread holding onto resources and not releasing them. Below is > > the main structure of our endpoint. Some parts have been removed or > > commented out, but it gets the basic structure across. > > > > We call "sendMessageToUser" in order to send a message to a client's > > browser. The issue that we have seen is if we breakpoint at the line > > that waits for the future to resolve, "future.get()", and reload the > > current client's browser, the endpoint becomes unusable where no > > messages can be sent or received any longer. Only a restart resolves > > the issue. We wanted to find out if our implementation of the > > asynchronous remote and future setup is correct or if there is a more > > appropriate use of the API? > > There have been some bugs fixed in this area. I'd suggest testing with > the latest 9.0.x release. > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org >
Thank you for the help. We upgraded to the latest version and don't see the issues any longer. We'll have to do some more extensive testing, but it looks good so far. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
