PQ59717: APPLICATION RUNNING IN A J2EE SERVER, APPLICATION RECEIVES LOADBMD FAILURE,APP SERVER REGION ARRAYINDEXOUTOFBOUNDSEXCEPTION

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
During J2EE Application execution, the application receives msg
BBOU0012W The function ORBEJSBridge::invoke_request(JNIEnv*,bboo
jorb*,char*,CORBA::Boolean,CORBA::Request*&,void*)_1936 recieved
CORBA system excetion CORBA::UNKNOWN.  Error code is C9C25790
java.rmi.ServerException: RemoteException occurred in server thr
ead; nested exception is:
com.ibm.ws390.csi.WS390Exception: Could not read key; nested exc
eption is:
com.ibm.ws390.csi.WS390Exception: failed calling loadBMD
.
The 'nested exception' in the above text, indicates that there
is a problem in the Application Server region, where the app. is
running.
In looking at the output of the application server region, we
see the following java stack trace:
com.ibm.ejs.container.ContainerException: loading bean meta data
  failed; nested exception is:
  java.lang.ArrayIndexOutOfBoundsException
com.ibm.ejs.container.EJSContainer.loadBeanMetaData
  (BeanMetaData.java:858)
com.ibm.ejs.container.loadBeanMetaData(EJSContainer.java:1212)
com.ibm.ws390.csi.WS390ContainerManager.loadBMD
  (WS390ContainerManager.java:717)
.
.
.
The important part of the above stack trace is the entry for
BeanMetaData.java, at line 858 of the java part.  If you see
this line number, in the stack trace, that is a good indicatr
that this APAR will address the problem.  In addition, the
problem should only occur on aplications that have not been
deployed using the SM/EUI levels that shipped with WebSphere
V4.01.  (If you have migrated from V4.0 to V4.01 and have
'migrated the apps', and NOT re-deployed them)
Local fix
If you re-deploy the application onto the J2EE application
server, using the correct level of the SM/EUI (the one shipped
with V4.01 or in maintenance for V4.01) then the application
should run correctly.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0.1 for z/OS and OS/390                   *
****************************************************************
* PROBLEM DESCRIPTION: Applications that were deployed on      *
*                      WebSphere Application Server V4.0 and   *
*                      migrated to WebSphere Application       *
*                      Server V4.0.1 may incur a               *
*                      ContainerException/                     *
*                      ArrayIndexOutOfBoundsException          *
*                      upon execution.                         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Applications that were deployed on a V4.0 level and migrated to
a V4.0.1 level may incur the following exception at runtime:

(Sample of stack trace that can be found in joblog)

com.ibm.ejs.container.ContainerException:
   loading bean meta data failed; nested exception is:
   java.lang.ArrayIndexOutOfBoundsException
java.lang.ArrayIndexOutOfBoundsException
.at com.ibm.ejs.container.BeanMetaData.<init>
  (BeanMetaData.java:858)
.at com.ibm.ejs.container.EJSContainer.loadBeanMetaData
  (EJSContainer.java:1212)
.at com.ibm.ws390.csi.WS390ContainerManager.loadBMD
  (WS390ContainerManager.java:717)
.at com.ibm.ws390.csi.WS390ContainerManager.loadBMDIfNeeded
  (WS390ContainerManager.java:783)
.at com.ibm.ws390.csi.WS390ContainerManager.keyToObject
  (WS390ContainerManager.java:568)
.at com.ibm.ws390.rmi.corba.ORBEJSBridge.invoke
  (ORBEJSBridge.java:399)
Problem conclusion
The Bean meta data load routine was fixed to properly handle
migrated applications.

APAR PQ59717 is associated with SERVICE LEVEL W401048 of
WebSphere Application Server V4.0.1 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ59717
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-04-03
Closed date 2002-04-23
Last modified date 2002-05-02

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:
UQ65518

Modules/Macros
BBOUBINF BBOZ0812 BBOZ0813      

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels
R401 PSY UQ65518    UP02/05/01 P F204

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ59717
IBM Group: Software Group
Modified date: May 2, 2002