Chapter 3. Web services problem determination 133
3.4.1 Check system integrity
When a WebSphere Application Server application is the Web service client and
receives an error, the simplest thing to do initially is to ensure that the Web
service provider is available and that the URL used by the requester is correct.
Clients attempting to access a provider with an incorrectly specified URL
commonly occurs when applications are moved from development environments
to production ones. Ports and host names most likely change, and clients must
be updated with the new Web service target URL.
3.4.2 Identify symptoms
Symptoms of a Web services problem appear in a variety of ways depending on
the problem, the client’s environment, and how the client was designed. For
example, if invoking an unmanaged client from the command-line console, the
error messages would be displayed to that interface. If the client is a Web
application that writes to an output stream that appears in the Web browser, then
the errors would be displayed to the browser. On the provider system, the
messages will appear in the application server SystemOut log.
Messages will, with a WSWS prefix indicate a Web services related error.
Problems may also occur that do not produce a Web services error message but
will appear as unexpected results in the application. A trace of the SOAP
messages often shows the error.
Specific symptoms covered in this activity include:
򐂰 Client system
javax.xml.rpc.ServiceException with message code WSWS5055E or
WSWS5014E.
For more information about this symptom see “targetNamespace contains
a non-traditional URI scheme” on page 118.
WSWS3713E: Connection to the remote host localhost failed. Received
the following error: Connection refused.
Verify that the host and port used to call the provider are correct.
Tip: When the Web service provider is an application running in WebSphere
Application Server, you can test the availability of the service by pointing a
browser to the URL. If the test is successful, you should see two lines. The
first contains the full QName of WSDL port, and the second the message Hi
there, this is a Web service!

Get WebSphere Application Server V6.1 Problem Determination: IBM Redpaper Collection now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.