Support Article
SOAP Service WSDL is failing when client call it
SA-30947
Summary
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(WSDLUtils.java:354)
at com.pega.pegarules.integration.engine.internal.util.PRServiceUtils.createWSDL(PRServiceUtils.java:594)
at com.pega.pegarules.integration.config.internal.util.WSDLUtils.serveWSDL(WSDLUtils.java:1876)
at
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.
Resolution
Delete the unwanted wsdl user jars from user DB to resolve the issue.
Published January 2, 2017 - 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.