APAR status
Closed as program error.
Error description
 All methods in Stateless Session Bean are configured for
"TRANSACTION_REQUIRED" and we use only container managed
transaction.
 SessionBean on receiving a call from JSP makes a call to RMI
server and then makes a JDBC call to DB.
 RMI Obj does not access DB nor there is a requirement for it
to participate in the transaction started by the container of SB
We tried both flavors of RMI
 RMI / JRPM - While making a call to RMI Obj, websphere
complains the stubs are not IIOP, hence it refuses to call any
RMI objects compiled with JRPM stubs.
( Why does Websphere NOT support RMI / JRMP objects, other
industry leading J2EE server like weblogic support it )
 RMI / IIOP - The call to RMI Obj goes thru fine, but the
subsequent call to JDBC fails, This as per your support group
is because just a simple RMI call puts the container managed
transaction in a whacky state and all further JDBC calls fail.
RMI object does not access any DB not tries to do anything with
transaction.. for demonstration the code inside RMI function can
just be a "return <...>;"
Local fix
N/A
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server 5.0 users who *
* make Object Transaction Service ( OTS ) *
* Inter ORB Protocol ( Interop ) calls to *
* servers that do not provide an OTS reply *
* context, or who make Remote Method *
* Invocation ( RMI ) calls to Java Virtal *
* Machines ( JVM ). *
****************************************************************
* PROBLEM DESCRIPTION: When a RMI call is made to a remote *
* server (not a WebSphere server) the *
* transaction is rolled back. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When an RMI call is made to a remote server (Not a WebSphere
server) an OTS Transactional Context is supplied with the call
to propagate the transaction ( Tx ) to the remote server. A
check was made to ensure that the remote server replied with an
OTS Context, if a context was not supplied on return then the Tx
was rolledback. The reply OTS context is optional so the check
was invalid and has been removed.
Problem conclusion
The ORB JTS Client Interceptor was modified to remove the check
for OTS reply contexts.
Temporary fix
Interim Fix PQ77038 sent to customer.
Comments
APAR information |
APAR number |
PQ77038 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00I |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2003-08-01 |
Closed date |
2003-09-18 |
Last modified date |
2003-09-25 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
|