IBM Support

PK90258: USER-DEFINED EXCEPTIONS EXTENDING JAVAX.XML.RPC.SOAP.SOAPFAULTEX CEPTION WILL NOT BE RECOGNIZED AS USER-DEFINED.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a user-defined exception extends
    javax.xml.rpc.soap.SOAPFaultException, the web services engine
    fails to recognize it as user-defined. This causes these
    types of exceptions to be written to the application server's
    JVM log, which is incorrect behavior.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Developers of WebSphere Application Server   *
    *                 web services with custom exceptions that     *
    *                 extend                                       *
    *                 javax.xml.rpc.soap.SOAPFaultException.       *
    *                                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Service-specific exceptions that are    *
    *                      thrown by a web service might appear    *
    *                      in the JVM log.                         *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If a web service application throws a service-specific
    exception, then that exception should not be logged to
    the JVM log. This is because service-specific exceptions do
    not indicate system errors, such as in the case of a
    java.lang.NullPointerException. These types of exceptions can
    be logged to trace if the user enables trace for
    com.ibm.ws.webservices.trace.UserExceptionTrace.
    However, if the exception extends
    javax.xml.rpc.soap.SOAPFaultException, the web services engine
    is not marking it as service-specific and therefore logs it
    to the JVM log.
    

Problem conclusion

  • The web services engine was fixed to accept this type of
    exception as service-specific.
    
    APAR PK90258 is currently targeted for inclusion in Service
    Level (Fix Pack) 7.0.0.5 of WebSphere Application Server V7.0.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK90258

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-06-30

  • Closed date

    2009-07-08

  • Last modified date

    2009-08-03

  • APAR is sysrouted FROM one or more of the following:

    PK78050

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

Modules/Macros

  • BBGUBINF BBOUBINF
    

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UK48201

       UP09/07/27 P F907

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.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 February 2022