Caught Exception while parsing XML Stream using Apply-Parse-XML
When I am trying to parse the XML using Apply-Parse-XML method, it is getting failed with exception "Fail: Caught exception parsing XML stream".
There is nothing much in logs as well. I can just see the following entry in log.
When I run the Parse XML rule and provide the same XML as input it works fine.
Could not see anything in the tracer as well, it just throws the same exception - Fail: Caught exception parsing XML stream
Has anyone come across such an issue? Is there any hot-fix for the same?
Any help in this regard will be appreciated.
Version: PEGA v7.1.6
Pegasystems Inc.
IN
Hello Prasad,
Can you set the log level to 'DEBUG' for the 'invokeaxis2' activity rule which will print the SOAP envelope details in PegaRULES log file, please share the pegarules logs
UnitedHealth Group
US
Hi Basavaraj,
I am not using any SOAP rule/service for this. All I am doing is taking XML as input parameter for an activity in a String param, Creating a Page of class Parse-XML rule and Apply-Parse-XML on the same page. I do not see invokeaxis2 activity being invoked in the tracer.
Regards,
Prasad
PEG
IN
Hi Prasad,
Is this environment upgraded from 6.x or a fresh?
Is this the first time you noticed this issue?
UnitedHealth Group
US
Hi Arvind,
The environment was upgraded from v5.4 to v7.1.6
I have noticed this issue in the new Activity that I have created while having the same Parse-XML rule.
It works fine with older activities that were created as part of v5.4.
Regards,
Prasad
PEG
IN
Hi Prasad,
Can you please perform below?
- Configure the Dynamic System Settings entry named "SwitchToOldAssembler" to true as shown below:
Owning Ruleset: Pega-IntegrationEngine
Purpose: SwitchToOldAssembler
Value: true - Restart the Application server.
UnitedHealth Group
US
Hi Arvind,
The value of DSS has already been set to true during migration
Regards,
Prasad
Accepted Solution
UnitedHealth Group
US
The issue is resolved. This was happening because the activity was truncating the XML which was being accepted as parameter String. Changing the design to send the value from PEGA property itself solved the problem.