Hi Brian, Thanks for the quick reply. Appreciate it. I got your point. This is really an issue with the XALAN jar in Sun. I thought it is a Xalan issue as the jar is still called xalan.jar. What I really meant to ask was if anyone else has faced this issue and if there is any alternative? Because when I tried using the new jar from xalan site and ran the JVM with the new jars, the application crashed. I am facing this problem in one of the interfaces which runs within Mule. And when we tried the new Jar, the Mule would not startup and we saw the exception , the trace of which I sent. Also attaching a screen shot from IBM heap analyzer which we are seeing and suggests that the biggest memory leak is happening in one of the Xalan class coming with the JVM. Any help is appreciated. thanks, Amit
Brian Minchau wrote: > > > > What is the evidence that this is an Apache Xalan-J issue? You wrote: > << > When we profiled the application and also analysed the heap dump, we found > that the issue was with Xalan. >>> > > The Apache Xalan-J classes have package names starting with > org.apache.xalan or org.apache.xml or org.apache.xpath. So which objects > are eating up memory, because your traceback doesn't show any of these. > > Also the exception you have occured in > com.sun.org.apache.xpath.internal.XPathAPI, which looks like your problem > is with SUN not Apache. Apache Xalan-J has this class: > org.apache.xpath.XPathAPI, and that sure looks like a SUN version of that > Apache class. > > - Brian > > > > > tareamit > <tare.a...@gmail. > com> To > xalan-j-users@xml.apache.org > 12/19/2008 05:17 cc > PM > Subject > OutofMemory issue in Xalan > > > > > > > > > > > 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: OutofMemory issue in Xalan > Sent from the Xalan - J - Users mailing list archive at Nabble.com. > > > > http://www.nabble.com/file/p21122167/Doc14.doc Doc14.doc -- View this message in context: http://www.nabble.com/OutofMemory-issue-in-Xalan-tp21098995p21122167.html Sent from the Xalan - J - Users mailing list archive at Nabble.com.
