Details
-
Bug
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
13.2.0, 13.2.1, 13.2.2, 13.3.0, 13.3.1, 13.4.0
-
None
-
None
-
Flagged
-
Platform 220 - Hardening, Platform 221 - 14.0 CodeFreeze
Description
After upgrading to v13.4 a customer kept going OOM on either MetaSpace or Compressed class space.
Tracing the classloading it seems like it's one class that's continuously loaded in a loop:
[Loaded org.hippoecm.hst.content.beans.standard.HippoDocument$Container$OLjiW79U$Relaxed$ZgrKVNEi from __JVM_DefineClass__] [Loaded org.hippoecm.hst.content.beans.standard.HippoDocument$Container$OLjiW79U$Relaxed$iekgtFC7 from __JVM_DefineClass__] [Loaded org.hippoecm.hst.content.beans.standard.HippoDocument$Container$OLjiW79U$Relaxed$HFzlBE5m from __JVM_DefineClass__] [Loaded org.hippoecm.hst.content.beans.standard.HippoDocument$Container$OLjiW79U$Relaxed$vui9voR4 from __JVM_DefineClass__] [Loaded org.hippoecm.hst.content.beans.standard.HippoDocument$Container$OLjiW79U$Relaxed$SlMK55mp from __JVM_DefineClass__] [Loaded org.hippoecm.hst.content.beans.standard.HippoDocument$Container$OLjiW79U$Relaxed$2WuE1ndz from __JVM_DefineClass__]
Disabling it (assuming you don't actually use dynamic beans) prevents the issue from occurring.
Attachments
Issue Links
- is duplicated by
-
HSTTWO-4664 Autogenerated beans do not work correctly for documents using taxonomy
- Closed
- relates to
-
HSTTWO-4622 Generate content blocks in runtime beans which include custom compound types
- Closed
- waits for
-
HSTTWO-4671 Improve runtime bean pojos to store more business logic
- Closed