Tomcat fixed the server usage so we should have a proper fix for tomee 7. in 1 week - time tomca is released.
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-12-03 12:08 GMT+01:00 tonywestonuk <[email protected]>: > Ok, not sure if this fix will make it to 1.7.3...., I notice you guys are > having a vote if 1.7.3 is going ahead... > > But, anyhow, I've now moved my websocket endpoint code into a separate > project that is hosted on Tomcat, which talks to tomee over multicast > sockets. I didn't realise that websockets can break the same origin > rule!....but as they can, I am able to do this easy. > > I think its a more scalable solution now anyhow, I can just add more tomcat > servers if I get too many people opening up too many persistent > connections. > And, while developing, that same project works in TomEE as im restarting > the > server every 5 mins anyhow so the bug does not cause me a problem. > > :-D > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/Websocket-Session-memory-leak-tp4676663p4677108.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
