Support Article
NullPointerException while invoking Connect SOAP in Pega7.1.7
SA-9648
Summary
NullPointerException observed while running Connect SOAP after upgrading to Pega 7.1.7. This functionality still working without any issues in PRPC 6.3.1.
Error Messages
2015-04-23 11:29:57,915 [ http-8443-7] [ STANDARD] [ ] [ MyCo:01.01.04] ( internal.mgmt.Executable) ERROR myco.com|1.1.1.1|Rule-Connect-SOAP.MYCO-Int-WebserviceImp-.getData MyCo01 - Exception
java.lang.NullPointerException
at com.pegarules.generated.activity.ra_action_invokeaxis2_11bc9e384251dd87ccf835ff8c84b922.step15_circum0(ra_action_invokeaxis2_11bc9e384251dd87ccf835ff8c84b922.java:4063)
at com.pegarules.generated.activity.ra_action_invokeaxis2_11bc9e384251dd87ccf835ff8c84b922.perform(ra_action_invokeaxis2_11bc9e384251dd87ccf835ff8c84b922.java:308)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375)
Steps to Reproduce
1. Recreate Connect SOAP after Pega7 Upgrade
2. Invoke Service
Root Cause
WS-Addressing was not supported by the external Service however it is being sent in SOAP Request message. Verified through SoapUI, no header element in Request message were sent in PRPC 6.3.1 and issue was caused due to WS-Addressing configuration enabled by the developer in Connect SOAP Rule.
Resolution
De-selecting WS-Addressing checkbox in Advanced tab of Connect SOAP Rule has resolved the issue.
Published May 7, 2015 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.