Close popover
Kiran Radha Manoj Turaga (KiranRadhaManojT)
American Express
Senior System Architect
American Express
KiranRadhaManojT Member since 2014 8 posts
American Express
Posted: October 26, 2015
Last activity: January 12, 2016

What's the Difference in log level setting for Soap Faults Exceptions in Pega6.2 & Pega7

HI Team,

We are getting lot of soap failure Exception in our production log files after Pega7 Upgrade, most of these failures are valid scenarios. Due to this log file size is getting huge. This behavior is not see in Pega 6.2, Can you please help us to achieve same behavior as Pega 6.2.


When we hit External system for particular service, if it sends Fail message in response automatically PEGA activity ‘InvokeAxis2’ handles SOAP fault message content and writes it in the log file which is used for debugging purpose(i.e.., OOTB Functionality) . When we trace same scenario in 6.2 we got the similar fail message for the ‘InvokeAxis2’ activity but the fail message is not getting logged in the log file.

Exception Name :

RemoteApplicationException : SOAP service failed

Caused by:

com.pega.apache.axis2.AxisFault: No Data found in DB

Valid Soap Faults :

- No Data Found in DB (Error Code : 500)

- Not valid Transactions


As an investigation I have compared the prlogging.xml files for Pega6.2 and Pega7 both are same.


So I would like to known from you,

Are there any new enhancements in Pega7 with respective Soap Faults Loggers ?

Why Soap Fails are getting logged only in Pega7 not in Pega6.2 ?

What shall we do to achieve same behaviour as Pega6.2 ?



Message was edited by: Kiran Radha Manoj Turaga

System Administration Upgrades Data Integration
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.