[XERCESJ-1751] Changing maxOccurs=unbounded to some finite number throws OOM in JVM

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.12.2
• Environment: Linux
• Assignee: Unassigned
• Reporter: Partha Pratim Paul
• Created: 15/Sep/22 09:52
• Updated: 15/Sep/22 20:26
• Resolved: 15/Sep/22 20:25

Description

Changing maxOccurs=unbounded to some finite number throws OOM in JVM. The finite number we have used is from 1000 to 5500 but the creates a memory starvation or resource exhaustion in all JVMs processing XMLs. 

The ask to let us know if -

1. Is there any boundary value that we can use for maxOccurs in our schema to overcome this issue?
2. Is there any fix available in the latest Xerces versions that we can upgrade to and that does not create this OOM exception? Our current version is 2.12.2
3. Is there any setting in the JVM (like Heap/Memory) that you recommend for us to use? The current heap size is 6GB for our JVMs
4. Is there any attribute that can be added to the schema to fix this issue

Issue Links

• duplicates: XERCESJ-1227 Poor performance / OutOfMemoryError for sequences, choices and nested with large minOccurs/maxOccurs