APAR status |
Closed as program error.
| Error description
WAS 3.5 is throwing different security exceptions then WAS 3.0.2
It seems that specific exceptions that were seen in 3.0.2 are
being replaced by a more general rollback exception in 3.5 Local fixProblem summary
exception, however the transaction code is suppressing the
security exception and throwing its own.
.
It appears that no matter what exception may be thrown by a bean
method, the com.ibm.ejs.csi.TransactionControlImpl.postInvoke()
method incorrectly supresses the original exception and throws a
CSITransactionRolledbackException.
.
The crux of the problem is that the
com.ibm.ejs.csi.TransactionControlImpl.postInvoke()
method makes a very poor assumption that its corresponding
preInvoke() method is always run, but this isn't the case. Problem conclusion
toCtrl collaborator's postInvoke was being called regardless of
whether its preInvoke was called, and the resulting exception
was masking the original security exception. In this fix,
greater care has been taken to keep track of the collaborators
on which the preInvoke was invoked, so as to match up the
corresponding postInvokes. Temporary fixComments
APAR information | APAR number | PQ44001 | Reported component name | WAS ADVANCED SU | Reported component ID | 5648C8402 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2000-11-30 | Closed date | 2001-01-10 | Last modified date | 2001-01-10 |
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 APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED SU | Fixed component ID | 5648C8402 |
Applicable component levels | R350 PSY | UP |
|