Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

SOAP Service WSDL is failing when client call it



User has created a soap service in the application and generated the WSDL URL.

When users hit the end point URL in the browser, instead of rendering the XML file in the browser, it shows status fail error, hence the users are unable to call the service and use it.

Error Messages

Error Logs :

2016-11-09 01:57:09,567 [http-bio-8383-exec-9] [ STANDARD] [ ] ( web.impl.WebStandardImpl) ERROR - null: Unhandled error in ETier invocation
java.lang.NoSuchMethodError: javax.wsdl.Types.removeExtensibilityElement(Ljavax/wsdl/extensions/ExtensibilityElement;)Ljavax/wsdl/extensions/ExtensibilityElement;
at com.pega.pegarules.integration.config.internal.util.WSDLUtils.createWSDL(
at com.pega.pegarules.integration.engine.internal.util.PRServiceUtils.createWSDL(
at com.pega.pegarules.integration.config.internal.util.WSDLUtils.serveWSDL(

Steps to Reproduce

Create a SOAP Service and generate a WSDL from Service package and try to hit it. While hitting URL user gets an error.

Root Cause

User QA DB has multiple wsdl jar's during runtime PRPC picking wrong jar version causing the issue.


Delete the unwanted wsdl user jars from user DB to resolve the issue.


Published January 2, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us