PK82801: WORK DONE AFTER TRANSACTION TIME OUT IN EJB DOES NOT ROLLBACK

Fixes are available

APAR status

Closed as program error.

Error description

If using an EJB with IBM RRA and using TX Required and a
Transaction Time out occurs, during post invoke of the EJB some
work might still be committed to the database instead of rolled
back.

Currently the problem does not happen with DB2.  But does happen
with all other supported databases.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server who use Enterprise Java Beans        *
****************************************************************
* PROBLEM DESCRIPTION: Work completed after transaction time   *
*                      out could be committed to database      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If using an Enterprise Java Bean with IBM RRA and Transaction
Time out occurs, during post invoke of the Enterprise Java
Bean work done after the time out but still with in the scope
of the bean transaction context might still be committed to
the database instead of rolled back. This can only happen if an
application continues to use a connection after a transaction
time out exception.

Currently the problem does not happen with DB2.  But does happen
with all other supported databases.

Problem conclusion

The APAR will not allow a connection that has an affinity to
a transaction that has already timed out, to be used for
anymore work.  Any attempts to use the connection after the
time out will result in an exception.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.0.2.37  6.1.0.27  7.0.0.7.  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
PK82801
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-03-17
Closed date
2009-06-16
Last modified date
2009-06-16

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
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 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":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK82801: WORK DONE AFTER TRANSACTION TIME OUT IN EJB DOES NOT ROLLBACK

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

R60A PSY

R60H PSY

R60I PSY

R60P PSY

R60S PSY

R60W PSY

R60Z PSY

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?