The stack trace is from the underlying xercers parser which is part of the
JDK. There was one issue reported for 3.1.2 with AIX which is also related to
xerces parser. From investigation, that was a bug in IBM JDK 6 SR 10 (SR 9
did not have the problem).