Errors returned to a client sending a SOAP request

What kind of problem are you seeing?

If none of these errors match the one you see:

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

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:

javax.security.cert.CertPathBuilderException: No end-entity certificate matching the selection criteria could 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 the: install_dir/installedApps/application_name.ear/soapsec.war/key/ directory. After replacing these files, you must stop and restart the application.

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

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.


Related tasks
Troubleshooting by task: What are you trying to do?
Troubleshooting by component: What is not working?
Related reference
Troubleshooting testing and first time run problems



Searchable topic ID:   rtrb_soapprobs
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/ae/rtrb_soapprobs.html

Library | Support | Terms of Use | Feedback