[jetty-users] SocketChannelEndpoint memory leak?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[jetty-users] SocketChannelEndpoint memory leak?

From: Matthias Pfau <matthias.pfau@xxxxxxxx>
Date: Mon, 18 Mar 2024 16:20:07 +0100 (CET)
Delivered-to: jetty-users@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/jetty-users/>
List-help: <mailto:jetty-users-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/jetty-users>, <mailto:jetty-users-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/jetty-users>, <mailto:jetty-users-request@eclipse.org?subject=unsubscribe>

Hi,
we are on jdk-21 and ran into a memory leak after the upgrade from jetty 11 to jetty 12.0.6.

Around 3.5 hours after server restart 72k instances of SocketChannelEndPoint consume 1GB of RAM.

Around 20 hours after server restart 75k instances of SocketChannelEndPoint consume 18GB of RAM.
Based on our current observations, the leak only occurs on nodes where we make use of Request#addIdleTimeoutListener and where we have heavy load. Could there be a relation to https://github.com/jetty/jetty.project/issues/10120?

Best,
Matthias

Follow-Ups:
- Re: [jetty-users] SocketChannelEndpoint memory leak?
  - From: Simone Bordet

Prev by Date: Re: [jetty-users] EXTERNAL- Re: websocket-jetty-server not able to upgrade request to websocket
Next by Date: Re: [jetty-users] SocketChannelEndpoint memory leak?
Previous by thread: [jetty-users] websocket-jetty-server not able to upgrade request to websocket
Next by thread: Re: [jetty-users] SocketChannelEndpoint memory leak?
Index(es):
- Date
- Thread

Breadcrumbs