IBM Support

PM18313: THE BEHAVIOR OF "THROWS EXCEPTION" IS NOT CLEARLY DEFINED BY THE SPECIFICATION AND CAUSES DEBATABLE RESULTS.

Fixes are available

7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • According to JSR 220 a non application related exception thrown
    by an EJB 3.0 application needs to be handled as an EJBException
    on the client side.  This method gets broken if the method
    signature of the EJB contains "throws Exception".
    Example:
    
    working case:
    public void ok() {throw new
    ArrayIndexOutOfBoundsException("ok");}
    //client receives an EJBException
    bad case:
    public void bad() throws Exception {throw new
    ArrayIndexOutOfBoundsException("nok");}
    //client receives an ArrayIndexOutOfBoundsException
    .
    Chapters 14.2.1 and 14.2.2 of JSR 220 final release define what
    is meant with application-exception and system-exception.  These
    definitions explain that an ArrayIndexOutOfBoundsExcepiton is a
    system-exception but no (!) application-exception. The tables
    shown in chapter 14.3 show explicitly that a system-exception
    should produce an EJBException on the client side if using
    Container Managed Transactions.
    .
    .
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0 who create Enterprise Java      *
    *                  Beans with "Exception" on a method throws   *
    *                  clause.                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: "throws Exception" on the throws        *
    *                      clause of an EJB method will cause a    *
    *                      RuntimeException to be handled as       *
    *                      application exception.                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    RuntimeExceptions are intended to be handled as
    non-application exceptions.  However, if "throws Exception" is
    on the throws clause of an EJB method WebSphere Application
    Server will handle RuntimeExceptions as if they were
    application exceptions.
    

Problem conclusion

  • A new system property,
    "com.ibm.websphere.ejbcontainer.declaredUncheckedAreSystemExcept
    ions" has been added.  When this property is set to "true" all
    RuntimeExceptions will be handled as non-application
    (Unchecked) exceptions regardless of whether "throws
    Exception" is on the throws clause of the EJB method.  In the
    V7.0 service stream the default value for this property will
    be "false".
    
    This property can be set in the WebSphere Administrative
    Console in the following way:
    
    1. Open the administrative console.
    2. Select Servers.
    3. Select Application Servers.
    4. Select the server you want to configure.
    5. In the Server Infrastructure area, select Java ¢â€ž ¢ and
    Process Management.
    6. In the Server Infrastructure area, select Process
    Definition.
    7. In the Additional Properties area, select Java Virtual
    Machine.
    8. In the Additional Properties area, select
    Custom Properties.
    9. Select the New box.
    10. In the Name entry field, type
    "com.ibm.websphere.ejbcontainer.declaredUncheckedAreSystemExcept
    ions".
    11. In the Value entry field, type "true".
    12. Select OK.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.13.  Please refer to the Recommended Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM18313

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-07-13

  • Closed date

    2010-08-06

  • Last modified date

    2010-08-06

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

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

Fix information

  • Fixed component name

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM18313

Modified date: 06 August 2010