I've never been successful trying to allocate more stack
space to the Java VM. The amount of heap space will make no difference to this
The most likely explanation for the different behaviour is
simply that your application code is using some of the stack space that would
otherwise be available to Saxon.
I can't really offer any other suggestions without seeing
your code. How deeply nested do you think its calls are?
(By the way, it's helpful if you can choose a subject line
that describes the problem. If everyone titled their posts as you have done, it
would become very difficult to find your way through the archives or through
I need help to understand why Saxon B 22.214.171.124 is behaving
differently depending if I use it from the command line or direclty from a
Using the command-line the stylesheet works perfectly and
the transformation generates as expected a good result.
Using Saxon from a
Java program and the same stylesheet caused the below
javax.xml.transform.TransformerException: Too many nested
apply-templates calls. The stylesheet may be looping.; SystemID: ...
For sure the source XML and the stylesheet are enought complex,
but I am surprised I cannot obtain the same result using one of the two
I tuned the VM to provide more heap memory or stack,
but the result was always the above error.
The error appears too early
in the transformation, and this surprise me more and more as the
transformation is enough long (less than half a minute) using the
What are the default memory settings for the Saxon B
Any ideas ?
I will appreciate very much any
Thank you in advance