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:
View install_dir/server_name/SystemErr.log and SystemOut.log for clues. See Viewing JVM logs for more information.
If you do not see a problem that resembles yours, or if the information provided does not solve your problem, see Troubleshooting help from IBM.
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:
In an installed application, these files are located in the: profile_root/installedApps/application_name.ear/soapsec.war/key/ directory.
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:
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.