I see, will it be "fixed" or should it be worked-around with a BackgroundProcess - that is what we use ATM in TomEE SNAPSHOT code?
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> 2015-11-04 8:57 GMT-08:00 Rémy Maucherat <r...@apache.org>: > 2015-11-04 17:46 GMT+01:00 Romain Manni-Bucau <rmannibu...@gmail.com>: > > > there is not only fireClose case I think, if the client disconnect > brutally > > you skip this part I think, isn't it? > > > > It is always called, but the websockets code isn't very rich on finally, so > if something really unexpected occurs during the close process, it won't > get called in some cases. It would need a finally on every line, so ... > > Rémy >
