APAR status |
Closed as unreproducible.
| Error description
The container creates ONE TX object PER transaction PER
container. When the beans are in two different app servers
(recreated on 1 machine, but two app servers and 2 machines)
exceptions thrown are correct - IllegalStateException and
TransactionRollback when using the setRollbackOnly method. When
they are in the same app server, this is when the bug manifests
itself. The transaction is rolledback but the exception is
trapped and not returned which could have other consequences.
The issue is in the BeanO.java file.
The customer provided us with a testcase on:
\\wasdoc0\wasus\mcohen\50124-500 The customer provided us with a testcase on:\\wasdoc0\wasus\mcohen\50124-500 Local fixProblem summary
****************************************************************
* USERS AFFECTED: All users of this release are affected. *
****************************************************************
* PROBLEM DESCRIPTION: See text below. *
****************************************************************
****************************************************************
No comments provided. Problem conclusionTemporary fixComments
No comments provided.
APAR information | APAR number | PQ47757 | Reported component name | WAS ADVANCED SU | Reported component ID | 5648C8402 | Reported release | 350 | Status | CLOSED UR1 | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-04-09 | Closed date | 2001-08-08 | Last modified date | 2001-08-16 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:
Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED SU | Fixed component ID | 5648C8402 | APAR is sysrouted TO one or more of the following:Modules/Macros
Applicable component levels | R350 PSN | UP |
|