PQ98297: APPLICATION SOAP FAULTS IN SYSPRINT/SYSOUT, SHOULD BE ABLE TO BE PREVENTED

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
When running WebSphere 5.02.008. Applications are generating
SOAP faults and are being logged into an application log file in
USS.
These SOAP fault messages (which include the JAVA stack, etc.)
are also being sent to SYSOUT/SYSPRINT. These messages should be
stopped from going to SYSOUT/SYSPRINT.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: With no com.ibm.ws.webservices.*        *
*                      tracing enabled,                        *
*                      WebServices DEBUG statements and        *
*                      Stack traces are appearing in the       *
*                      SYSOUT and SYSPRINT logs.               *
*                                                              *
*                      In addition, User-defined WebService    *
*                      Exceptions- An exception which is       *
*                      defined in the WSDL (WebServices        *
*                      Definition Language) for a given        *
*                      operation and may be thrown by the      *
*                      service endpoint to indicate "normal"   *
*                      processing- are being outputted         *
*                      to both the SYSOUT and SYSPRINT logs    *
*                      as System Exceptions.                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
com.ibm.ws.webservices.* debug statements are appearing
in the SYSOUT and SYSPRINT logs when no tracing is enabled.
These debug statements should only appear if tracing is
explicitly enabled.

In addition, User Exceptions should not be handled by the
WebServices Engine as System Exceptions, for example:

FunctionName: com.ibm.ws.webservices.engine.WebServicesFault
SourceId: com.ibm.ws.webservices.engine.WebServicesFault
Category: DEBUG
ExtendedMessage: The following exception was logged;
     <Application-specific exception>
at <Application-specific classes...>
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.webservices.engine.providers.java.RPCProvider.
  invokeMethod(RPCProvider.java:404)
at com.ibm.ws.webservices.engine.providers.java.RPCProvider.
  processRequestResponse(RPCProvider.java:296)
at com.ibm.ws.webservices.engine.providers.java.RPCProvider.
  processMessage(RPCProvider.java:262)
at com.ibm.ws.webservices.engine.providers.java.JavaProvider.
  invoke(JavaProvider.java:289)
at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(
  PivotHandlerWrapper.java:212)
at com.ibm.ws.webservices.engine.handlers.WrappedHandler.invoke
  (WrappedHandler.java:61)
at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke
  (PivotHandlerWrapper.java:212)
at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke
  (PivotHandlerWrapper.java:212)
at com.ibm.ws.webservices.engine.WebServicesEngine.invoke
  (WebServicesEngine.java:255)
Problem conclusion
WebServices debug statements are now properly wrapped with
conditional statements that only allow the messages to appear
when com.ibm.ws.webservices.* tracing is enabled.

User Exceptions are now not printed to SYSPRINT and/or SYSOUT
logs by default. Instead a new tracing statement has been
created:

  com.ibm.ws.webservices.trace.UserExceptionTrace=all=enabled

that when enabled will output the User Exception caught as
well as the exceptions corresponding Stack Trace.

APAR PQ98297 is associated with SERVICE LEVEL W502025 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ98297
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-12-12
Closed date 2005-03-08
Last modified date 2005-04-01

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:
PQ98298

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UK01263    UP05/03/14 P F503

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PQ98297.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ98297
IBM Group: Software Group
Modified date: Apr 1, 2005