Thank you very much for your tips - of course they will help us (every performance improvement is higly welcome)!
But back to our leaks: Have you any idea, where they could come from? Thomas > > > --- Urspr�ngliche Nachricht: --- > Datum: 01.02.05, 16:14 > Von: "Hall, Joe" <[EMAIL PROTECTED]> > An: then <[EMAIL PROTECTED]> > Betreff: RE: Re: memory leak in xalan 2 > > I don't think it needs to be synchronized if you use only instance data. > Here is a link on the xalan site about using it in multi-threaded > environment (http://xml.apache.org/xalan- > j/usagepatterns.html#multithreading). You can synch creation of the > template cache then reads should be ok to access it without the overhead. > > The way you describe this, you can only do 1 transformation at a time. > This would be a huge performance penalty. > > I hope this helps. > > Joe > > P.S. I've noticed increased performance by using translets. > http://xml.apache.org/xalan-j/xsltc_usage.html > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 01, 2005 3:39 AM > To: [EMAIL PROTECTED] > Cc: John Gentilin > Subject: WE: Re: memory leak in xalan 2 > > Yes, you are right. We are caching the templates of the xsl documents that > we use. > Perhaps it is also important to say, that xalan is used to generate a > servlets' output stream, so we are in a multithreading environment. The > function that generates the output is marked as synchronized (non-static) > and it is the only place where xalan is used in this application. > > Thomas > > P.S.: I appologize, if you get this email twice. I am not really familiar > whith posting mails to this mailing list... :) > > > > > > > --- Urspr�ngliche Nachricht: --- > > Datum: 31.01.05, 22:25 > > Von: John Gentilin <[EMAIL PROTECTED]> > > An: THEN <[EMAIL PROTECTED]> > > Betreff: Re: memory leak in xalan 2.6.0? > > > > Is just the XML data held in memory or are you trying to cache XSL > > transformers also ?? > > If so are you caching Transformers or Templates ?? > > > > -John G > > > > [EMAIL PROTECTED] wrote: > > > > >Hello, > > > > > >we use xalan 2.6.0 with xerces 2.6.2 on BEA Weblogic Server V8.1. We > > configured the JRE that both, xalan and xerces, are prepended to the > > bootclasspath (-Xbootclasspath/p:.../lib/xercesImpl.jar:.../lib/xml- > > apis.jar:.../lib/xalan.jar). > > > > > >We use xalan to transfer xml streams that are hold in memory to html > > output that is sent back as response to the client. We use XSLT > > standard 1.0. > > > > > >Since we suspected a meory leak, we used a profiling tool to inspect > > >our > > application. And the profiler "said" that two leaks have their home in > > the xalan/xerces code part. > > > > > >Here are excerpts from the 2 stack traces that the profiling tool > > >gave us > > as result (I can send you the full screen shots if you need them): > > > > > >------------------------------------------------ > > >The first trace (a leak of type char[]): > > >------------------------------------------------ > > >org.apache.xalan.transformer.TransformerImpl.transform() > > >... > > >org.apache.xml.dtm.ref.DTMManagerDefault.getDTM() > > >weblogic.apache.xerces.parsers.AbstractSAXParser.parse() > > >weblogic.apache.xerces.parsers.XMLParser.parse() > > >weblogic.apache.xerces.parsers.DTDConfiguration.parse() > > >... > > >weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocume > > >nt() > > >... > > >weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanAttrib > > >ute() > > >weblogic.apache.xerces.xni.XMLString.toString() > > >-------------------------------------- > > > > > >------------------------------------------------ > > >The second trace (a leak of type int[]): > > >------------------------------------------------ > > >org.apache.xalan.transformer.TransformerImpl.transform() > > >... > > >org.apache.xml.dtm.ref.DTMManagerDefault.getDTM() > > >weblogic.apache.xerces.parsers.AbstractSAXParser.parse() > > >weblogic.apache.xerces.parsers.XMLParser.parse() > > >weblogic.apache.xerces.parsers.DTDConfiguration.parse() > > >... > > >weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocume > > >nt() > > >... > > >weblogic.apache.xerces.impl.XMLNameSpaceBinder.startElement() > > >... > > >org.apache.xml.dtm.ref.sax2dtm.SAX2DTM.startElement() > > >org.apache.xml.dtm.ref.DTMDefaultBase.indexNode() > > >org.apache.xml.dtm.ref.DTMDefaultBase.ensureSizeOfIndex() > > >-------------------------------------- > > > > > >Is this a known bug? We would be very happy if you were able to help > > >us > > to remove those 2 leaks. > > > > > >Thanks in advance! > > > > > >Thomas > > > > > > > > > > > > > > >-- > > >Ein Service von http://www.sms.at > > > > > > > > > > > > > > -- > Ein Service von http://www.sms.at > -- Ein Service von http://www.sms.at
