Direct link to fix
APAR status
Closed as program error.
Error description
When you execute BPEL applications that contain large XML documents and complex XSL stylesheets (for example, in mediation flows), you receive a java.lang.VerifyError with a stack trace similar to the following stack trace in the FFDC logs: [11/3/17 20:47:00:106 UTC] FFDC Exception:java.lang.VerifyError SourceId:com.ibm.ws.sca.internal.message.impl.MessageDispatcherI mpl.processMessageWithPCI ProbeId:720 Reporter:com.ibm.ws.sca.internal.message.impl.MessageDispatcherI mpl@255cfad2 java.lang.VerifyError: JVMVRFY012 stack shape inconsistent; class=Transform_SC_To_Canonical_res, method=http$colon$$slash$$slash$ProdMgmt_SC_Med$slash$xslt$slash $Transform_SC_To_Canonical_res$colon$Transform_SC_To_Canonical_r es2$outline$0(LTransform_SC_To_Canonical_res$1;)V, pc=46796 Exception Details: Location: Transform_SC_To_Canonical_res.http$colon$$slash$$slash$ProdMgmt_ SC_Med$slash$xslt$slash$Transform_SC_To_Canonical_res$colon$Tran sform_SC_To_Canonical_res2$outline$0(LTransform_SC_To_Canonical_ res$1;)V @46796: JBaload Reason: Type top (current frame, locals[6]) is not assignable to 'reference' type Current Frame: bci: @46796 flags: { } locals: { 'Transform_SC_To_Canonical_res', 'Transform_SC_To_Canonical_res$1', 'com/ibm/xslt4j/org/apache/rnm1/xml/serializer/SerializationHand ler', 'java/lang/Object', 'com/ibm/xslt4j/org/apache/rnm1/xalan/xsltc/DOM', integer, top, top, 'Trasform_SC_To_Canonical_res', 'com/ibm/xslt4j/org/apache/rnm1/xml/dtm/DTMAxisIterator', top, top, top, top, top, top, top, top, top, top, top, top, top, top, top, top, top, top, 'com/ibm/xslt4j/org/apache/rnm1/xml/dtm/DTMAxisIterator', top, 'com/ibm/xslt4j/org/apache/rnm1/xml/dtm/DTMAxisIterator' } stack: { 'Transform_SC_To_Canonical_res$1', integer, 'com/ibm/xslt4j/org/apache/rnm1/xml/serializer/SerializationHand ler', 'java/lang/String' } at java.lang.J9VMInternals.newInstanceImpl(Native Method) at java.lang.Class.newInstance(Class.java:1899) at com.ibm.xslt4j.org.apache.rnm1.xalan.xsltc.trax.TemplatesImpl.ge tTransletInstance(TemplatesImpl.java:437) at com.ibm.xslt4j.org.apache.rnm1.xalan.xsltc.trax.TemplatesImpl.ne wTransformer(TemplatesImpl.java:466)
Local fix
In your modules, use lazy parsing instead of eager parsing as the business object parsing mode.
Problem summary
IBM BPM uses the XSLT processor from the XSLT4J library in BPEL processes and mediation flows. This XSLT processor can't handle large and complex XSL stylesheets, which causes a java.lang.VerifyError when you use a Java 8 runtime environment. PRODUCTS AFFECTED IBM Business Process Manager (BPM)
Problem conclusion
An interim fix that uses the XSL transformation built into the IBM JDK that comes with WebSphere instead of the XSLT4J library is available for IBM BPM V8.6 CF2017.09 on Fix Central.
Temporary fix
Not applicable
Comments
APAR Information
APAR number
JR59039
Reported component name
BPM ON CLOUD
Reported component ID
5725L6300
Reported release
860
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-01-26
Closed date
2018-02-22
Last modified date
2018-02-22
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
BPM
Fixed component ID
5737A5700
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFPJS","label":"IBM Business Process Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.6.0.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
14 September 2022