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
After a few days of use of the Shibboleth Identity Provider under moderate load, service stops working. Sometimes with high-CPU or sometimes with idle CPU. It appears that Jetty just "stops". I think that some JVM threads may still be working as some background tasks sometimes produce lines in the log after the web service has stopped.
Looking at a heap dump from an instance in the broken state using Eclipse MAT, the "Leak Suspects" report shows two suspects:
One instance of org.eclipse.jetty.io.ArrayRetainableByteBufferPool$Bucket loaded by org.eclipse.jetty.start.Classpath$Loader @ 0x807fafb0 occupies 1,036,941,960 (48.84%) bytes. The memory is accumulated in one instance of java.lang.Object[], loaded by <system class loader>, which occupies 1,036,941,768 (48.84%) bytes.
One instance of org.eclipse.jetty.io.ArrayRetainableByteBufferPool$Bucket loaded by org.eclipse.jetty.start.Classpath$Loader @ 0x807fafb0 occupies 1,036,853,888 (48.83%) bytes. The memory is accumulated in one instance of java.lang.Object[], loaded by <system class loader>, which occupies 1,036,853,696 (48.83%) bytes
The "Histogram" shows a lot of byte[] objects which appears to be many instances similar to:
Description
After a few days of use of the Shibboleth Identity Provider under moderate load, service stops working. Sometimes with high-CPU or sometimes with idle CPU. It appears that Jetty just "stops". I think that some JVM threads may still be working as some background tasks sometimes produce lines in the log after the web service has stopped.
Stack trace is available here: stack.txt
Looking at a heap dump from an instance in the broken state using Eclipse MAT, the "Leak Suspects" report shows two suspects:
org.eclipse.jetty.io.ArrayRetainableByteBufferPool$Bucket
loaded byorg.eclipse.jetty.start.Classpath$Loader @ 0x807fafb0
occupies 1,036,941,960 (48.84%) bytes. The memory is accumulated in one instance ofjava.lang.Object[]
, loaded by<system class loader>
, which occupies 1,036,941,768 (48.84%) bytes.org.eclipse.jetty.io.ArrayRetainableByteBufferPool$Bucket
loaded byorg.eclipse.jetty.start.Classpath$Loader @ 0x807fafb0
occupies 1,036,853,888 (48.83%) bytes. The memory is accumulated in one instance ofjava.lang.Object[]
, loaded by<system class loader>
, which occupies 1,036,853,696 (48.83%) bytesThe "Histogram" shows a lot of
byte[]
objects which appears to be many instances similar to:We think this is
MonoEntries
not being released from the pool but do not know where.How to reproduce?
Currently unknown
The text was updated successfully, but these errors were encountered: