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

Fixes are available

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 &#162;&#226;&#158; &#162; 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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

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

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?