SA-16634

Summary

Recently migrated from PEGA 6.2SP1 to 7.1.6. Now the failure responses for soap service calls logged as ERROR level in PegaRules log.

Error Messages

(PEGA 6.2 ) :

2015-10-16 03:20:46,289 [read.pool t=009bdc68] [TABTHREAD3] [ your_App:01.01.01] (your_class.Action) INFO your_host|127.0.0.1 your_id - SOAP Service failed

( PEGA 7.1) :

2015-10-16 02:38:51,153 [ch Thread t=009b8840] [TABTHREAD2] [ your_app:01.01.01] ( internal.mgmt.Executable) ERROR your_host|127.0.0.1|Rule-Connect-SOAP.your_class.your_Activity-.your_Activity your_id - Exception
com.pega.pegarules.pub.services.RemoteApplicationException: SOAP service failed
at com.pegarules.generated.activity.ra_action_invokeaxis2_c7367a7b950d78597cad7f60b4e360bf.step15_circum0(ra_action_invokeaxis2_c7367a7b950d78597cad7f60b4e360bf.java:4049)
at com.pegarules.generated.activity.ra_action_invokeaxis2_c7367a7b950d78597cad7f60b4e360bf.perform(ra_action_invokeaxis2_c7367a7b950d78597cad7f60b4e360bf.java:308)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3275)………..
…….
…….
Caused by:
com.pega.apache.axis2.AxisFault: com.abc.xyz.service.FaultResponseMessage
at com.pega.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:446)

Steps to Reproduce

1. Use Connect-SOAP to call an external service that returns SOAP fault failure.

Root Cause

This issue was determined to be a product enhancement request as the current behavior is expected.
 

Resolution

Perform the following local-change: Modify invokeAxis2 step # 15 code 

Throwable cause = e.getCause();

  if (cause != null && cause instanceof java.io.IOException)

    throw new ResourceUnavailableException("SOAP service failed", cause);

  else

   throw new RemoteApplicationException("SOAP service failed", e);

}

 
and replace 
   throw new RemoteApplicationException("SOAP service failed", e);
with
   oLog.error("SOAP service failed", e);