Dunbar, Norman (Capgemini) wrote:
> Hi Eddie,
> 
> I'm not the world's greatest XML/XSLT/DocBook/Java guru, but it appears to me 
> that the error is coming from the Saxon XSLT processor. So, while your XML is 
> valid and correct, it's hitting some limit inside the Saxon utility - that 
> limit looks like the Java stack.
> 
> I notice from the errors that you are using DocBook - have you got sections 
> within sections within sections or similar, that are nested quite deeply? It 
> could be this that is causing the processor to barf.
> 
> The problem, looking at  the Saxon mailing list thread here :
> 
> http://markmail.org/message/m476x6ntpq4n562q#query:saxon%20TransformerException%20%22Too%20many%20nested%20apply-templates%22+page:1+mid:idrf6wvgglxqasu6+state:results
> 
> could be because the Java system hasn't got enough stack space, so maybe the 
> following might help:
> 
> * Try running the conversion using the command line utility "xslutilc.bat" as 
> found in your bin folder, where XSL FO is installed. See section 2.5 in the 
> manual(s) found in your doc folder.
> 
> * If that still fails, edit the file and find this line, at the end:
> 
> "%java%" -Xss4m -Xmx512m -classpath "%jars%" com.xmlmind.xslutil.Start %*
> 
> The -Xss4m sets the Java stack size to a maximum of 4Mb. You can probably 
> fiddle with this setting to see if you get further. Try 8Mb or higher to see 
> if it gets fuirther through your transform before barfing or even, if it 
> actually works to completion.
> 
> 
> I'm sorry but I have not tested the above. For details of the command line 
> usage, see section 2.5 in the manual. (Found in your doc folder).
> 
> 

Everything you say is correct and thank you for explaining this.

In our experience, Saxon 6 or 9 is rock solid and does not consume a lot
of heap space and even less stack space (4Mb is already a pretty large
stack space).

Therefore we would say that the problem found by Eddie comes either from
a very peculiar DocBook document or from a bug in the DocBook XSL
stylesheets. In both cases, we really need the input file causing the
problem in order to find out what happens.



> Cheers,
> Norman.
> 
> Norman Dunbar
> Contract Senior Oracle DBA
> Capgemini Database Team (EA)
> Internal : 7 28 2051
> External : 0113 231 2051 
> 
 
--
XMLmind FO Converter Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xfc-support

Reply via email to