|
Problem(Abstract) |
User exceptions that are defined by a web services
developer will get logged in the SystemOut.log in WebSphere® Application
Server V5 by default. This may be undesirable if the user exceptions are
supposed to occur during normal operation. |
|
|
|
Cause |
This is a limitation. Unfortunately there is no way to
eliminate the user exceptions from appearing in the SystemOut.log in
WebSphere Application Server V5. This limitation does not occur in
WebSphere Application Server V6. |
|
|
Resolving the
problem |
The solution is to upgrade to WebSphere Application Server
V6. Go to the Information Center article Tracing
Web services that describes this behavior.
Here is a relevant excerpt:
======================
You can enable logging of user-defined exceptions by specifying the
com.ibm.ws.webservices.trace.UserExceptionTrace=all trace string. The
user-defined exceptions are not logged by default. A user-defined
exception is an exception that is defined in the Web Services
Description Language (WSDL) file for an operation.
A user-defined exception often indicates an error-free condition. For
example, the user-defined OverdrawnException exception, can occur for
the service endpoint implementation of the makeWithdrawl method. This
exception indicates an expected condition and does not indicate an error
in the service endpoint implementation. Because these types of
exceptions can occur during normal processing, they are not logged by
default. When a user-defined exception is logged, the information is
sent to the trace.log file and not to the SystemOut.log file.
You can also use the following trace strings to enable tracing for
user-defined exceptions, as well as other trace points:
* com.ibm.ws.webservices.*=all
Turns on all Web services run-time trace logs.
* com.ibm.ws.webservices.trace.*=all
Turns on MessageTrace and UserExceptionTrace.
======================
This means that if the service or client is running WebSphere Application
Server V6, the customer will not see his exceptions logged to
SystemOut.log, unless he sets trace specification to do so. The customer
must upgrade to 6.0 to take advantage of this functionality. |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|