Problem:
BBOIVPE jobs sysout:
Trace: 2002/03/28 21:51:04.441 01 t=7D41D8 c=UNK
key=P8 (00000004)
Description: Throw CORBA system exception
exception id: CORBA::UNKNOWN
minor code: c9c25790
from filename: ./bboosyse.cpp
at line: 757
Trace: 2002/03/28 21:51:04.444 01 t=7D41D8 c=UNK
key=P8 (00000005)
Description: Catch CORBA system exception
exception id: CORBA::UNKNOWN
minor code: c9c25790
from file: ./bbooejsb.cpp
at line: 1893
IVP has failed
/tmp/ejbivp.err'
BossLog: { 0001} 2002/03/28 21:51:04.439 01
SYSTEM=A200 CLIENT=UTOIVPE
p+749 ... BBOU0011W The function
CORBA::throw_sysexcp(const char*,ULong
UNKNOWN. Error code is C9C25790.
BossLog: { 0002} 2002/03/28 21:51:04.443 01
SYSTEM=A200 CLIENT=UTOIVPE
p+1893 ... BBOU0012W The function
ORBEJSBridge::invoke_request(JNIEnv*,b
received CORBA system exception CORBA::UNKNOWN.
Error code is C9C25790.
java.rmi.ServerException: RemoteException occurred
in server thread; nes
java.rmi.RemoteException: java.rmi.RemoteException:
javax.transaction.T
0 No; nested exception is:
org.omg.CORBA.TRANSACTION_ROLLEDBACK:
com.ibm.websphere.csi.CSITransact
at
com.ibm.ws390.csi.WS390TxStrategy.handleException(WS390TxStrategy.ja
at
com.ibm.ws390.csi.WS390TransactionControl.postInvoke(WS390Transactio
at
com.ibm.ejs.container.EJSContainer.postInvoke(EJSContainer.java:1947
at
com.ibm.ws390.samples.ivp.ejb.EJSRemoteBMPPolicyBMPHome.findByPrimary
C9C25790 in BBOIVPE indicates there is a problem on
the server a client
is trying to talk to. In this case, the client is
BBOIVPE and the
server is BBOASR2(S). You can also tell the exception
happened on the
server side by the following that is included in the
exception on
BBOIVPE:
"java.rmi.ServerException: RemoteException occurred in
server thread;
nested exception is"
- In the exception on BBOIVPE, there are following
calls in the callback stack:
at
com.ibm.ejs.container.EJSContainer.postInvoke
at
com.ibm.ws390.samples.ivp.ejb.EJSRemoteBMPPolicyBMPHome.findByPrimaryKey
Since findByPrimaryKey is involved, it's looking for
the Policy object's key in the database created by the BBOICD job using
DB2 JDBC interfaces.
When this fails, this usually indicates some problem
with the JDBC
setup.
From BBOASR2S job output:
Obtaining an initial context
Running a bmp bean
Lookup bmp policy home
Narrow bmp home
Finding bean1 - 1111
--> ** DB2 ERROR: Received an UnstatisfiedLinkError
trying to retrieve the Driver DLL build version!!
SQLException loading DLL/registering JDBC
Driver
SQLSTATE is FFFFF
SQLCODE is -1
java.sql.SQLException: --> ** DB2 ERROR: DB2 for
OS/390 SQLJ/JDBC
Driver level mismatch detected **
--> ** DB2 ERROR: Driver Classes build=DB2 7.1
PQ54756
--> ** DB2 ERROR: Native DLL build=Unknown due to
UnsatisfiedLinkError:
DLL is likely downlevel.
java.sql.SQLException: DB2SQLJConnection error in
native method:
constructor: RRS "CREATE THREAD" failed using DB2
system:DBW1,
Plan:DSNJDBC , RC=08 and REASON=00f30034
Possible Solutions:
- Make sure BBOASR2S steplib, if DB2 is required to be
STEPLIB'ed to on this system, includes DB2's SDSNLOAD, SDSNLOD2, and
SDSNEXIT datasets. And check any other procs you have that STEPLIB to the
DB2 code, specifically for JDBC access, stop and restart BBOASR2, and
rerun BBOIVPE.
- Check if the DB2 maintenance (look for latest in PSP
Bucket) has been applied correctly to the SDSNLOD2 dataset and the hfs for
DB2 as well. Both MUST be in sync, otherwise you will get this "Driver
level mismatch detected" message. UQ61107 in particular is required for
running the IVP successfully. There is an IVP for JDBC that DB2 ships and
describes in the DB2 manuals how to run it. It may be helpful to verify
that sample for JDBC first and then approach the WebSphere IVP.
|