+

Search Tips   |   Advanced Search

Application client sending SOAP request receives errors


  1. Overview
  2. SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket; java.net.ConnectException: Connection refused: connect
  3. javax.security.cert.CertPathBuilderException: No end-entity certificate matching the selection criteria can be found.


Overview

Browse the appserver logs. Look up any error or warning messages in the message table.

Review appserver logs...

See also:

  1. UDDI, Web service, and SOAP component troubleshooting tips
  2. Troubleshooting help from IBM
  3. IBM Support
  4. IBM Support - Must Gather

 

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

This refused connection may have been sent to the default port, 80, and an HTTP server is not installed or configured. To verify, send message directly to the SOAP port; for example, to http://hostname:8007. If the message is sent correctly, there are two ways to resolve the problem:

 

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:

In an installed application, these files are located in...

install_dir/installedApps/myapp.ear/soapsec.war/key/

After replacing these files, stop and restart the application.

To replace these files in a SOAP-enabled application not yet installed:

  1. Expand the myapp.ear file.
  2. Expand the soapsec.war file.
  3. Replace the security key files in the key/ directory.
  4. Install the application and restart the server.





 

Related tasks

Troubleshooting Web services
Application deployment troubleshooting tips