Hi Scott,

First, sorry for the lame bug report. I understand that i'm putting a mess
on the process by doing this. Did simply lost my brain on this one. You have
the right to kill me next time.

Apart from that, your fix works like a charm.
I'm also (and I'm sure you will) be very pleased to see that memory usage
significantely dropped.

For the figures, a 3.24MB XML file needs 68MB of memory with your fix while
it needed up to 198MB of memory with Xalan 2.0.0.

It spits out approx. 5500 files (total of 5.2MB), transform time is
equivalent w/ both distrib, . This is certainly due to I/O overhead.

-- 
 St�phane Bailliez 
 Software Engineer, Paris - France 
 iMediation - http://www.imediation.com 
 Disclaimer: All the opinions expressed above are mine and not those from my
company. 



> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Monday, July 09, 2001 5:29 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [Xalan 2.2D6] EmptyStackException
> 
> 
> 
> Stephane, thank you for the bug report.  I replicated the 
> bug, and just
> checked in a fix.  I sent you a jar offline to try.
> 
> It is better for us if you can post bug reports to
> http://nagoya.apache.org/bugzilla/.  It helps us track them, 
> do triage on
> them, and create regression tests.
> 
> -scott
> 
> 
> 
> 
>                                                               
>                                                         
>                     Stephane                                  
>                                                         
>                     Bailliez                To:     
> [EMAIL PROTECTED]                                          
>                     <sbailliez@imedi        cc:     (bcc: 
> Scott Boag/CAM/Lotus)                                       
>                     ation.com>              Subject:     
> [Xalan 2.2D6] EmptyStackException                            
>                                                               
>                                                         
>                     07/09/2001 07:28                          
>                                                         
>                     AM                                        
>                                                         
>                     Please respond                            
>                                                         
>                     to xalan-dev                              
>                                                         
>                                                               
>                                                         
>                                                               
>                                                         
> 
> 
> 
> 
> I just gave a try to Xalan 2.2D6.
> Besides the fact that I have apparently some EOL spitted out 
> to the console
> (that do not show up in Xalan 2.0), it crashes after some successful
> output.
> 
> Ths stylesheet makes heavy use of the redirect extension to 
> generate some
> javadoc-like report.
> If you have any recommendation about the xsl style concerning 
> either style,
> speed, memory...i'd be glad to read them. I'd be very curious 
> to know what
> are the patterns that are so memory consuming (about 200MB 
> for Xalan 2.0
> with an XML file of 3MB)
> 
> Works fine with Xalan 2.0 from JAXP 1.1 / xerces 1.4.1 but 
> fails with Xalan
> 2.2D6
> 
> See the XML and XSL attached in zip file.
> 
> java -Xms128M -Xmx256M -cp .\lib\xalan.jar 
> org.apache.xalan.xslt.Process
> -in
> small-coverage.xml -xsl coverage-frames.xsl -EDUMP -PARAM output.dir
> "coverage"
> [...]
> javax.xml.transform.TransformerException
>         at
> org.apache.xalan.transformer.TransformerImpl.transformNode(Tra
> nsformerImpl.j
> 
> ava:1151)
>         at
> org.apache.xalan.transformer.TransformerImpl.transform(Transfo
> rmerImpl.java:
> 
> 590)
>         at
> org.apache.xalan.transformer.TransformerImpl.transform(Transfo
> rmerImpl.java:
> 
> 1037)
>         at
> org.apache.xalan.transformer.TransformerImpl.transform(Transfo
> rmerImpl.java:
> 
> 1015)
>         at org.apache.xalan.xslt.Process.main(Process.java:839)
> ---------
> java.util.EmptyStackException
>         at java.util.Stack.peek(Stack.java:82)
>         at java.util.Stack.pop(Stack.java:64)
>         at
> org.apache.xalan.transformer.TransformerImpl.popMode(Transform
> erImpl.java:27
> 
> 41)
>         at
> org.apache.xalan.templates.ElemApplyTemplates.execute(ElemAppl
> yTemplates.jav
> 
> a:231)
>         at
> org.apache.xalan.templates.ElemApplyTemplates.transformSelecte
> dNodes(ElemApp
> 
> lyTemplates.java:423)
>         at
> org.apache.xalan.templates.ElemApplyTemplates.execute(ElemAppl
> yTemplates.jav
> 
> a:226)
>         at
> org.apache.xalan.transformer.TransformerImpl.executeChildTempl
> ates(Transform
> 
> erImpl.java:2096)
>         at
> org.apache.xalan.transformer.TransformerImpl.applyTemplateToNo
> de(Transformer
> 
> Impl.java:1927)
>         at
> org.apache.xalan.transformer.TransformerImpl.transformNode(Tra
> nsformerImpl.j
> 
> ava:1120)
>         at
> org.apache.xalan.transformer.TransformerImpl.transform(Transfo
> rmerImpl.java:
> 
> 590)
>         at
> org.apache.xalan.transformer.TransformerImpl.transform(Transfo
> rmerImpl.java:
> 
> 1037)
>         at
> org.apache.xalan.transformer.TransformerImpl.transform(Transfo
> rmerImpl.java:
> 
> 1015)
>         at org.apache.xalan.xslt.Process.main(Process.java:839)
> 
> --
>  St�phane Bailliez
>  Software Engineer, Paris - France
>  iMediation - http://www.imediation.com
>  Disclaimer: All the opinions expressed above are mine and 
> not those from
> my
> company.
> 
> 
> 
> 
> 
> 

Reply via email to