Problem and Symptoms:
BBOIVPE jni GetMethodID S0C4 abend . Running BBOIVPE results in the
following output in BBOASR2S:
Starting Tran1
Obtaining an initial context
Running a bmp bean
Lookup bmp policy home
Narrow bmp home
Finding bean1 - 1111
Then an S0C4 abend in jni_GetMethodID occurs and an SVC dump is
produced:
COMPON=WEBSPHERE Z/OS, COMPID=5655A9801,ISSUER=BBORLEXT,ABEND IN
*PATHNAM/jni_GetMethodID
PIDS/5655A9801 RIDS/#PATHNAM#L RIDS/#PATHNAM AB/S00C4 PRCS/00000010
REGS
RIDS/BBORLEXT#R
Symptom Description
------- -----------
PIDS/5655A9801 Program id: 5655A9801
RIDS/#PATHNAM#L Load module name: #PATHNAM
RIDS/#PATHNAM Csect name: #PATHNAM
AB/S00C4 System abend code: 00C4
PRCS/00000010 Abend reason code: 00000010
REGS/03188 Register/PSW difference for R03: 188
RIDS/BBORLEXT#R Recovery routine csect name: BBORLEXT
HER SERVICEABILITY INFORMATION
Recovery Routine Label: BBORLEXT
Date Assembled: 01226
Module Level: cb4xh01
Subfunction: CB_SRV_REG
Possible Solutions:
- check DB2/JDBC maintenance on the System where WebSphere V4.01 is
being run. In the PSP bucket for WAS 4.01, (UPGRADE WASAS401, SUBSET
WAS401), there is a list 'cross product maintenance'. This is in addition
to maintenance that is included in the install logic of the product. The
DB2 / JDBC maintenance that we have seen cause this problem are:
UQ59417,UQ59415,and UQ59527. Refer to PSP for latest maintenance.
- This DB2 maintenance ships code that is in the 'hfs' for DB2 on the
z/OS system. Verify that the hfs is mounted, that the maintenance has been
correctly applied/copied to the DB2 hfs, and the hfs path for this DB2
maintenance is correct in the libpath of the WebSphere Servers that need
it.
=============================================================================
Problem and symptoms:
Running BBOIVPE results in the following output in BBOASR2S:
Obtaining an initial context
Running a bmp bean
Lookup bmp policy home
Narrow bmp home
Finding bean1 - 1111
Finding bean2 - 7777
Adding 11 to the amount for both beans
Setting premium for bean1 to 150
Setting premium for bean2 to 300
Starting Tran2
Obtaining an initial context
Lookup bmp policy home
Narrow bmp home
Find the bean with key - 7777
java.sql.SQLException: DB2SQLJConnection error in native method:
connectReuse() SQLSTATE=FFFFF and SQLCODE=-1
:at COM.ibm.db2os390.sqlj.jdbc.DB2SQLJConnection.setError
(DB2SQLJConnection.java:1923)
:at
COM.ibm.db2os390.sqlj.jdbc.DB2SQLJConnection.setError(DB2SQLJConnect
:at
COM.ibm.db2os390.sqlj.jdbc.DB2SQLJConnection.connectReuse(DB2SQLJCon
:at
com.ibm.db2.jcc.DB2PooledConnection.getConnection(DB2PooledConnectio
:at
com.ibm.db2.jcc.DB2ConnectionCache.getConnection(DB2ConnectionCache.
:at
com.ibm.db2.jcc.DB2DataSource.getConnection(DB2DataSource.java:153)
:at
com.ibm.db2.jcc.DB2DataSource.getConnection(DB2DataSource.java:129)
:at
com.ibm.ws390.samples.ivp.ejb.PolicyBMPBean.getConnection(PolicyBMPB
:at
com.ibm.ws390.samples.ivp.ejb.PolicyBMPBean.ejbFindByPrimaryKey(Poli
:at
com.ibm.ws390.samples.ivp.ejb.EJSBMPPolicyBMPHomeBean.findByPrimaryK
:at
com.ibm.ws390.samples.ivp.ejb.EJSRemoteBMPPolicyBMPHome.findByPrimar
:at
com.ibm.ws390.samples.ivp.ejb._PolicyBMPHome_Stub.findByPrimaryKey(_
:at
com.ibm.ws390.samples.ivp.ejb.PolicySessionBean.tran2(PolicySessionB
:at
com.ibm.ws390.samples.ivp.ejb.EJSRemoteStatelessPolicySession.tran2(
When the BBOASR2S address space is initializing, it produces the
following messages:
WS/390 trace settings file:
/WebSphere390/CB390/controlinfo/envfile/
BBOASR2A/trace.dat
WS/390 trace setting: *=all=enabled
WS/390 trace spec: *=all=enabled
java.lang.ClassNotFoundException:
com.ibm.ws390.connmgmt.ConnectionFactoryBuilder
:at java.net.URLClassLoader.findClass(URLClassLoader.java:240)
:at java.lang.ClassLoader.loadClass(ClassLoader.java:517)
:at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:440)
:at java.lang.ClassLoader.loadClass(ClassLoader.java:449)
:at java.lang.Class.forName1(Native Method)
:at java.lang.Class.forName(Class.java:142)
:at
com.ibm.ws390.csi.WS390ContainerManager.<init>(WS390ContainerManager
.java:175)
:at com.ibm.ws390.rmi.corba.ORBEJSBridge.initCSI(ORBEJSBridge.java:184)
parser moduleTypes:
Possible Solutions:
- check your Java version. If its release 20011015 (SR11 UQ99325), you
may want to move to 20011206 (SR12 UQ61198) because of some problems with
SR11 or modify the way you run your IVPs. When running BBOIVPE in batch,
the job has 2 steps. 1st step is 'BMP' then 2nd step is 'CMP'. The problem
is that in batch, the first step starts, starts a JVM, and executes. Then
the step ends, and the jvm goes away. Second step starts, and during the
'initialize of the jvm'...it fails. The SR11 PTF had ++HOLD, that says you
can run thru the sample webapps, to drive the CMP /BMP. Or you could break
the BBOIVPE job into 2 separate jobs with 2 separate shell scripts, or
comment out the 2nd step in the shell script, run it, then change the
comments to comment out the 1st step, and execute the 2nd.
- check DB2 maintenance (ref to PSP). Make sure UQ59417 was applied to
the "target" libraries and was copied to the linklist library. If it
wasn't copied it means DB2 maintenance hit the DB2 "erly" code and the new
code was not being picked up. DB2 "erly" code requires an IPL to be picked
up. Re-IPL the system and rerun BBOIVPE.
|