You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am observing a rather interesting behavior. I have upgraded from Jetty9.x to Jetty 10.0.24
My security team is running a HTTP2 Fuzz workload from Defensix on this Jetty server.
While doing this, we have observed that the application POD in Kubernetes goes OOM killed. But the heap memory used by the application is just 2Gb (total POD limit is 16G).
I have been able to isolate almost everything else. Could this be due to related to Jetty?
Could this be due to non-heap usage of my application? The jcmd command shows almost 10G in "Others".
Can Jetty consume so much non-heap memory?
Any pointers would be much appreciated.
Thanks
The text was updated successfully, but these errors were encountered:
Jetty Version
Jetty-10.0.24
Jetty Environment
Jetty server
Java Version
JDK11
Question
I am observing a rather interesting behavior. I have upgraded from Jetty9.x to Jetty 10.0.24
My security team is running a HTTP2 Fuzz workload from Defensix on this Jetty server.
While doing this, we have observed that the application POD in Kubernetes goes OOM killed. But the heap memory used by the application is just 2Gb (total POD limit is 16G).
I have been able to isolate almost everything else. Could this be due to related to Jetty?
Could this be due to non-heap usage of my application? The jcmd command shows almost 10G in "Others".
Can Jetty consume so much non-heap memory?
Any pointers would be much appreciated.
Thanks
The text was updated successfully, but these errors were encountered: