RE: Suspected memory leak of org.apache.coyote.AbstractProtocol$ConnectionHandler object while using Websocket

2018-02-02 Thread Serge Perepel
Any takers to tackle this issue? -Original Message- From: Serge Perepel [mailto:se...@american-data.com] Sent: Friday, January 26, 2018 2:33 PM To: Tomcat Users List Subject: RE: Suspected memory leak of org.apache.coyote.AbstractProtocol$ConnectionHandler object while using Websocket

RE: Suspected memory leak of org.apache.coyote.AbstractProtocol$ConnectionHandler object while using Websocket

2018-01-26 Thread Serge Perepel
}; } function closeSocket(){ console.log("close webSocket"); if (webSocket) webSocket.close(); } You need to run it on multiple clients if you want it leak fast. We did it with 8 clients and it leaked 3GB with in like 10 min. Thank you [http://www

RE: Suspected memory leak of org.apache.coyote.AbstractProtocol$ConnectionHandler object while using Websocket

2018-01-26 Thread Serge Perepel
Forgot to mention that we are running Tomcat 8.5 on Windows 2012 Server -Original Message- From: Serge Perepel [mailto:se...@american-data.com] Sent: Friday, January 26, 2018 9:12 AM To: users@tomcat.apache.org Subject: Suspected memory leak of org.apache.coyote.AbstractProtocol

Suspected memory leak of org.apache.coyote.AbstractProtocol$ConnectionHandler object while using Websocket

2018-01-26 Thread Serge Perepel
import javax.websocket.Session; import javax.websocket.server.ServerEndpoint; import ad.common.Global; import ad.ecs.async.AsyncEngine; import ad.ecs.async.AsyncResponse; import ad.ecs.async.AsyncType; import ad.ecs.db.DatabaseEngine; import ad.ecs.db.paradox.User; import ad.ecs.security.engine.Security