Application client SOAP request troubleshooting tips

Use this information to diagnose and troubleshoot problems with clients sending SOAP requests.

What kind of problem are you seeing?
If none of these errors match the one you see:
  • Browse the application server logs. Look up any error or warning messages in the message table.

    [AIX Solaris HP-UX Linux Windows][IBM i]View install_dir/server_name/SystemErr.log and SystemOut.log for clues. To learn more, see the viewing JVM logs information. For additional tips, see the Universal Discovery, Description, and Integration, Web service, and SOAP component troubleshooting tips information.

    Note: This topic references one or more of the application server log files. As a recommended alternative, you can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM® i systems. You can also use HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access all of your log and trace information using the LogViewer command-line tool from your server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.

If you do not see a problem that resembles yours, or if the information provided does not solve your problem, see the troubleshooting help from IBM information.

SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket; java.net.ConnectException: Connection refused: connect

The most likely cause of this refused connection is that it was sent to the default port, 80, and an HTTP server is not installed or configured.

To verify this situation, send the message directly to the SOAP port; for example, to http://hostname:9080. If the message is sent correctly, there are two ways to resolve the problem:
  • Continue specifying port 9080 on SOAP requests.
  • If an HTTP server is not installed, install one and the associated plug-in component.
  • If an HTTP server is installed:
    • Regenerate the HTTP plug-in configuration in the administrative console by clicking Environment > Update WebServer Plugin, and restarting the HTTP server.
    • If the problem persists, view the HTTP server access and error logs, as well as the plugin_install_root/logs/web_server_name/http_plugin.log file for more information.

javax.security.cert.CertPathBuilderException: No end-entity certificate matching the selection criteria can be found

This error usually indicates that new or updated security keys are needed. The security key files are:
  • SOAPclient
  • SOAPserver
  • sslserver.p12

[AIX Solaris HP-UX Linux Windows][z/OS]In an installed application, these files are located in the: install_dir/installedApps/application_name.ear/soapsec.war/key/ directory. After replacing these files, you must stop and restart the application.

[IBM i]In an installed application, these files are located in the: profile_root/installedApps/application_name.ear/soapsec.war/key/ directory.

[IBM i]After replacing these files, you must stop and restart the application. The profile_root variable refers to the profile_rootND/profiles/profile_name directory

To replace these files in a SOAP-enabled application that is not yet installed:
  • Expand the application_name.ear file.
  • Expand the soapsec.war file.
  • Replace the security key files in the key/ directory.
  • After you replace these files, install the application and restart the server.

For current information available from IBM Support on known problems and their resolution, see the IBM Support page.

IBM Support has documents that can save you time gathering information needed to resolve this problem. Before opening a PMR, see the IBM Support page.