[AXIOM-34] Sometimes accessing an AXIOM tree while the underlying input stream is closed causes an OutOfMemoryError

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 1.2.8
• Environment: Mac OS X; java version "1.5.0_13"; AXIOM revision 686026
• Assignee: Andreas Veithen
• Reporter: Andreas Veithen
• Created: 14/Aug/08 20:52
• Updated: 27/Mar/11 11:42
• Resolved: 16/Dec/08 12:20

Description

Under some circumstances, accessing an AXIOM tree while the underlying input stream is closed doesn't throw a proper exception but causes an OutOfMemoryError. The attached Java code provides an example of this behavior.

Issue Links

• relates to: SYNAPSE-406 Validation mediator causing 100% CPU utilization with large schema, never produces results
• relates to: SYNAPSE-440 XML > 4000 chars published through SimpleURLRegistry gets StackOverflow
• relates to: AXIOM-67 Handling of xml documents with two top level elements is errorneous
• relates to: AXIOM-232 XML Element lost when there is an OMException inside OMChildrenIterator.next()
• relates to: AXIOM-110 Careless exception handling needs to be fixed