PM65856: UNABLE TO USE USERTRANSACTION AS ARGUMENT TO REMOTE METHOD

7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• The following IllegalStateException may be thrown when
  UserTransaction is used as an argument to a remote method...
  
  java.lang.IllegalStateException: UserTransaction accessed
  outside EJB method
  at
  com.ibm.ejs.container.UserTransactionWrapper.readObject(UserTran
  sactionWrapper.java:592)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at
  sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
  Impl.java:60)
  at
  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
  AccessorImpl.java:37)
  at java.lang.reflect.Method.invoke(Method.java:611)
  at
  com.ibm.rmi.io.IIOPInputStream.invokeObjectReader(IIOPInputStrea
  m.java:1809)
  at
  com.ibm.rmi.io.IIOPInputStream.inputObjectUsingClassDesc(IIOPInp
  utStream.java:1529)
  at
  com.ibm.rmi.io.IIOPInputStream.inputObjectClassDesc(IIOPInputStr
  eam.java:1504)
  at
  com.ibm.rmi.io.IIOPInputStream.readSerializable(IIOPInputStream.
  java:1178)
  at
  com.ibm.rmi.io.IIOPInputStream.simpleReadObjectInternal(IIOPInpu
  tStream.java:460)
  at
  com.ibm.rmi.io.IIOPInputStream.simpleReadObjectLoop(IIOPInputStr
  eam.java:545)
  at
  com.ibm.rmi.io.IIOPInputStream.simpleReadObject(IIOPInputStream.
  java:497)
  at
  com.ibm.rmi.io.ValueHandlerImpl.readValue(ValueHandlerImpl.java:
  210)
  at com.ibm.rmi.iiop.CDRReader.read_value(CDRReader.java:1578)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server V7.0 users *
  *                  of remote Enterprise Java Beans (EJBs)      *
  ****************************************************************
  * PROBLEM DESCRIPTION: UserTransaction cannot be passed as     *
  *                      an argument to an in-process remote     *
  *                      method if the argument size is large.   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a remote method is called on an EJB that is running in
  the same process, the ORB optimizes the marshalling and
  demarshalling of arguments by using a temporary byte array.
  If the arguments are large and the byte array would grow too
  large, the ORB uses a secondary thread for demarshalling.  If
  the EJB container UserTransaction object is demarshalled on
  the secondary thread, it is unable to find thread data from
  the main thread, and it fails.
  

Problem conclusion

• The EJB container UserTransaction object no longer searches
  for thread data while being demarshalled.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 7.0.0.25.  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 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