Support Article

Expecting WS-Addressing header even when WS-Addressing is off

SA-33765

Summary



The user is getting below error as response when the provider send back the response without header in PEGA. Moreover this service is consumed by multiple other consumers without any issue, and the provider is claiming why PEGA is looking for custom header when the WSDL of the provider doesn’t even support that custom header.

"A required header representing a Message Addressing Property is not present "

GCS -- Found that below Hfixes need to be shipped.
HFIX-20726
HFIX-24415


Error Messages



015-08-10 13:12:30,279 [ WebContainer : 16] [ STANDARD] [ ] [ AcqFW:01.01.11] (ngineinterface.service.HttpAPI) ERROR dcentral1214.intra.aexp.com|10.65.204.5 ajeffr - 10.65.204.5: com.pega.pegarules.pub.PRRuntimeError
com.pega.pegarules.pub.PRRuntimeError: PRRuntimeError
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(ThreadRunner.java:707)
at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.runActivitiesAlt(PRThreadImpl.java:435)
at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.runActivities(HttpAPI.java:3252)
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequestInner(EngineAPI.java:384)
at sun.reflect.GeneratedMethodAccessor81.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)


Steps to Reproduce



Issue can be recreated when a response from provider is coming back with the blank header


Root Cause



A defect in Pegasystems’ code or rules

Resolution



Apply HFix- 24415

Published February 15, 2017 - Updated February 18, 2017

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.