In our web application we are getting a outofmemory exception. When we profiled the application and also analysed the heap dump, we found that the issue was with Xalan. I also came across the following bug in Jdk1.5.
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6434840 The resolution in this bug was a work around which required adding the latest xalan 271 jar file. But when I add the latest jar file, my application does not even start and gives the following exception. onException: Could not instantiate bean class [com.tuc.hrcp.interfaces.db.HRCPDataSource]: Constructor threw exception; nested exception is java.lang.NoClassDefFoundError: com.sun.org.apache.xpath.internal.XPathAPI at org.apache.commons.digester.Digester.createSAXException(Digester.java:2919) at org.apache.commons.digester.Digester.createSAXException(Digester.java:2945) at org.apache.commons.digester.Digester.endElement(Digester.java:1133) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.endNamespaceScope(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.commons.digester.Digester.parse(Digester.java:1685) at org.mule.config.builders.AbstractDigesterConfiguration.process(AbstractDigesterConfiguration.java:101) This is a huge issue right now and is causing us a lot of pain and customer problems. It seems that there is no fix for this as of now??? -- View this message in context: http://www.nabble.com/OutofMemory-issue-in-Xalan-tp21098995p21098995.html Sent from the Xalan - J - Users mailing list archive at Nabble.com.
