PM59231: EJB POSTINVOKE NOT BEING CALLED DURING NOTIFYEXCEPTION

Fixes are available

APAR status

Closed as program error.

Error description

During a Webservices invoked EJB, exceptions can be encountered
and not handled properly because the EJB postInvoke method is
not being run during NotifyException.

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server using JAX-WS webservices.            *
****************************************************************
* PROBLEM DESCRIPTION: In cases where an exception occurs in   *
*                      an EJB that was invoked as part of a    *
*                      web service, appropriate post cleanup   *
*                      is not done.                            *
****************************************************************
* RECOMMENDATION:  Apply the fix pack that contains the fix.   *
****************************************************************
When an error occurs in an web services invoked EJB, it is
essential to clean up the state and transaction.
We currently call the cleanup method before we send a response
back to the client but not during exception processing. This
behavior could cause a transaction to remain active on a
thread and prevent a transaction associated with the current XA
flow from resuming.

Problem conclusion

Postinvoke is now called when an exception occurs so cleanup
is performed.

The following JVM property needs to be set -
com.ibm.websphere.websvcs.EJBPostInvokeCallOnException=true to
turn on this behavior.

For more details on how to set the JVM property,
refer to the article "Java virtual machine custom properties"
in the Information Center for your WebSphere Application
Server version and operating system.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.25, 8.0.0.4, and 8.5.0.1  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
PM59231
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
2012-02-28
Closed date
2012-06-01
Last modified date
2012-06-01

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
R800 PSY
UP
R850 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"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:
28 October 2021

Tips

PM59231: EJB POSTINVOKE NOT BEING CALLED DURING NOTIFYEXCEPTION

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

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?