saxon trips bug in JIT compiler requiring exclusion clause

[simonp]

Pretty much skyrocketing memory usage the moment anything XSLT is done when running under jdk 1.6 20. Looked into the hs error file and found:

Current CompileTask?: C2:880 ! net.sf.saxon.event.ReceivingContentHandler?.startElement(......)

Turning that into google produced a link to something that makes everything settle down nicely:

 http://www.devcomments.com/Saxon-JVM-crash-Out-of-swap-space-OOM-error-withsolution-at89036.htm

Later simplified to adding:

-XX:CompileCommand=exclude,net/sf/saxon/event/ReceivingContentHandler.startElement"

Also found to be a problem in jdk 1.5.0_22

[simonp]

Fixed in svn rev 6483