IV22700: XML TRANSFORMERCONFIGURATIONEXCEPTION THROWN AFTER MIGRATION FRO M XALAN-J TO XML XL-TXE
Closed as program error.
Error Message: javax.xml.transform.TransformerConfigurationException: <OSB>ERR 0614<CSB> The processor has encountered an internal error condition. Please report the problem and provide the following information: corrupt! . Stack Trace: javax.xml.transform.TransformerConfigurationException: com.ibm.xtq.xslt.jaxp.HandledRuntimeException: <OSB>ERR 0614<CSB> The processor has encountered an internal error condition. Please report the problem and provide the following information: corrupt! at com.ibm.xtq.xslt.jaxp.AbstractTransformerFactory.newTemplates(Un known Source) at palani.XsltProcessorFactory.buildTemplates(XsltProcessorFactory. java:400 ) at palani.XsltProcessorFactory.buildTransformer(XsltProcessorFactor y.java:3 38) at palani.XsltProcessorFactory.buildTransformer(XsltProcessorFactor y.java:3 29) at palani.TestXslJavaExtension.testXsltc(TestXslJavaExtension.java: 45) at palani.TestXslJavaExtension.main(TestXslJavaExtension.java:31) Caused by: com.ibm.xtq.xslt.jaxp.HandledRuntimeException: <OSB>ERR 0614<CSB> The processor has encountered an internal error condition. Please report the problem and provide the following information: corrupt! at com.ibm.xtq.xslt.jaxp.ConfigurationErrorHandler.report(Unknown Source) at com.ibm.xtq.utils.Reporter.report(Unknown Source) at com.ibm.xtq.ast.parsers.xslt.XSLTParser.reportError(Unknown Source) at com.ibm.xtq.xslt.drivers.XSLTCompiler.compile(Unknown Source) at com.ibm.xtq.xslt.jaxp.compiler.TransformerFactoryImpl.createTemp lates(Un known Source) ... 6 more . N/A
Here follows three workarounds: 1) Avoid the compilation parameter "split limit": The problem occurred only when the 'split limit' parameter has been passed to the compiler. If 'split limit' parameter is not specified, the compiler takes the default option and compile the Stylesheet correctly. The down side is that compilation takes more time and can get a warning message suggesting to use 'split limit' parameter to improve the compilation speed. 2)Switch the processor to interpret mode: For more information refer "Migrating to XL-TXE" section of the Java Infocenter. This option has performance impact as interpretation takes more time compared to compiled code. 3) Split the large templates to smaller functional units: When the Stylesheet has one or more larger templates, break them into smaller functional units. For example, by using xsl:call-template to break part off as a subroutine or by relying more heavily on xsl:apply-templates rather than xsl:for-each.This provides more explicit points at which the code can be divided in addition to those deduce automatically and thereby avoid the bug.
Problem has happened while Stylesheet compiler attempted to arrange the generated byte-code into smaller units (less than 64K) when the generated byte-code units are greater than the JVM limit of 64K.
This defect will be fixed in: 6.0.0 SR11 . JVM has been modified to properly split the Stylesheet to smaller units when the generated bytecode units are greater than 64K.
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels
Translate this page: