Troubleshooting web services and outbound web service integrations
Learn how to solve problems that you may have when using web service integration steps in your services.
The following table describes some common problems that you might encounter when creating services that include web service and outbound web service integration steps:
| Issue | Symptom or error message when you click discover | Possible resolutions |
|---|---|---|
| Malformed URL exception | CWLLG0594E: An exception occurred while initializing the runnable thread. Error: com.lombardisoftware.component.common.workflow.WorkflowProcessItemException: java.net.MalformedURLException | Because the WSDL is protected, the runtime environment reads the value in the EndpointAddress input field only, not the value in the EndpointAddress in the WSDL file, a missing or incorrect value in the EndpointAddress input field causes the web service invocation to fail. Enter or correct the value in the EndpointAddress input field. |
| Incorrect WSDL URI value | PARSER ERROR: Problem parsing '[path_name]\webAPIService.':The markup in the document following the root element must be well formed. | You have incorrectly typed the URI value.
Navigate to the URI using a web browser to verify that you have the
correct WSDL. A common problem is that the For file protocol URIs, the URI does not exist on disk. If you are unable to validate the location of the URI on disk, contact your network administrator. |
| Wrong WSDL URL | SystemOut.log shows an exception: SERVER_ERROR_DISCOVERING_WSDL_DATA javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR: Problem parsing 'WSDL_URL'.: org.xml.sax.SAXParseException: The element type "body" must be terminated by the matching end-tag "</body>". |
You might have typed the WSDL URL incorrectly. Or the web service is not activated on the server. View the contents of the URL in a browser that can display an XML response, for example, Firefox. |
| The WSDL URL produces an empty response. | SystemOut.log shows an exception:
SERVER_ERROR_DISCOVERING_WSDL_DATA_CAUSE org.xml.sax.SAXParseException: Premature end of file. |
You might have specified the URL of the web service rather than the WSDL file. Try appending "?wsdl" or "?WSDL" to the URL. |
| Missing types | SystemOut.log shows an exception: java.lang.RuntimeException: Unable to find Type Descriptor for element ={NAMESPACE}TYPE |
You are using the desktop Process Designer and have not pressed and completed the "Generate Types..." wizard in the web service or its server. |
| Duplicate Business Objects | Warnings in the screens presented by the "Generate Types..." wizard. | You are using the desktop Process Designer and your Process App or Toolkit already has Business Objects of the same name in it or its dependencies. Either remove these business objects or the dependencies to the toolkits that define them (if this is possible without causing damage to the Process App), or click through the "Generate Types..." wizard and accept the warnings. |
| Nonexistent host | Unknown Host Exception | You have incorrectly typed the host value. Navigate to the URI using a web browser to verify that you have the correct host information. The server that hosts the URI is offline (not running). Contact your network administrator to determine if this is causing the problem. The network is experiencing connectivity problems. Contact your network administrator to determine if this is causing the problem. |
| Authentication required for WSDL access | Runtime Exception: Unauthorized access to '[path_name]\webAPIService?WSDL' | The WSDL URI is protected by an authentication mechanism. If you have permission to access the web service, check the Protected WSDL check box, and then enter the Username and Password . Navigate to the WSDL URI using a web browser and save the text of the WSDL to a file so that you can use the file location as the target WSDL URI. |
| Invocation of the web service fails | org.apache.axis2.AxisFault: HTTP ( 500 ) Internal Server Error | The WSDL definitions in the cache are no longer compatible with the web service provider definitions. To fix this problem, clear the cache using the BPMClearWSICache command command. |
| Your business process, running on Linux, contains a series of outbound web services. The WSDL of your web service contains a large number of XML Schema Definition (XSD) files. When you discover the WSDL or generate data types in IBM® Process Designer, a failure occurs. | You have too many open files ... | IBM Business Automation Workflow requires more file handlers to load and parse a large WSDL file at a peak time. Your operating system, Linux, might not have enough file handlers available at that time. Increase the value of the nofile parameter in your /etc/security/limits.conf file. If your main WSDL file is calling many other WSDLs and XSDs, consider merging these files into one WSDL file. |