Java mapping in ccBPM works in PI 7.0 but fails in PI 7.1

Question

Hi guys,
at the moment we are upgrading form SAP PI 7.0 to SAP PI 7.11.
In a scenario for processing of incoming orders we use an ccBPM.
In this ccBPM there is an mapping where the original xml document of the order are combined with some
additional information form an web service (multi mapping 2 => 1)
The result of this mapping is processed further to create an sales order in the backend.
The multi mapping an java mapping is used.
Now we are testing the scenario with PI 7.11 and it fails at this mapping step.
in the workflow log following error occurs.
An exception with the type CX_ST_MATCH_ELEMENT occ urred, but was neither handled locally, nor de
Message no. W8899
I tested the same message on out SAP PI 7.0 system and the whole ccBPM works well.
When I extract the 2 messages from workflow log and paste them into the test tab of the operation mapping of Enterprise Service Builder of SAP PI 7.11, surrounding by the envelope used by multi mappings
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
   <ns0:Message1>
               XML MESSAGE 1
   </ns0:Message1>
   <ns0:Message2>
               XML MESSAGE 2  
   </ns0:Message2>
</ns0:Messages>
the mapping works without error, but at runtime it fails, throwing the error mentioned above.
What could be the reason for this error?
Does the multi mapping change in PI 7.11 at runtime?
Could it be a problem parsing the multi message?
Any help appreciated.
Kind regards
Jochen

Answer 1

Hi Raja,
thanks for your suggest.
I know this issue, the java class files are compiled using jdk 1.5.
We made some more tests.
e.g. created an dummy ccBPM with two mappings, one two spilt the incoming message in two messages (graphical message mapping) and one to merge this two messages to one message again (java mapping)
the mapping works at design time on test tab, but fails with the same error at rumtime.
Also we tested one single operation mapping with this two mappings (split via graphical mapping and merge via java mapping)
This works also at design time but fails at runtime with a similar error shown in smq2
The error message is Error ST_MATCH_FAIL occured. P1=element-start P2=M
we tried to add the whole incoming message to the trace by
getTrace().addWarning()
but an trace object is never created in for this step in the workflow log.
it seem whether you can not add trace messages using the command or that the error occures before this command will be used.
Kind regards
Jochen