[
https://issues.jboss.org/browse/WFLY-3976?page=com.atlassian.jira.plugin....
]
Stuart Douglas commented on WFLY-3976:
--------------------------------------
Alpha2 is the most up to date, and it most likely to have it solved, but it is likely
solved in both.
Memory leak in Websocket implementation (8.1.0 Final)
-----------------------------------------------------
Key: WFLY-3976
URL:
https://issues.jboss.org/browse/WFLY-3976
Project: WildFly
Issue Type: Bug
Components: Web Sockets
Affects Versions: 8.1.0.Final
Environment: CentOS 7
Java 1.7.0_65-b17
Reporter: Veli Cris
Assignee: Stuart Douglas
Priority: Critical
Creating 100k persistent websockets connections, exchanging small strings (with
RemoteEndpoint.Basic) and finally disconnecting all connections the memory grows with ~1GB
for each 100k. Basically the test is the following: the clients are connecting and sending
a hello message to the server; the server is responding with a welcome string and the
clients are disconnecting.
The settings in onOpen() callback are:
session.setMaxBinaryMessageBufferSize(10240);
session.setMaxTextMessageBufferSize(10240);
session.setMaxIdleTimeout(120000);
session.getUserProperties().put("ts", System.currentTimeMillis());
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)