Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Migration from WAS 3.5.x to 4.0.1

0 views
Skip to first unread message

shalini

unread,
Aug 28, 2002, 9:46:07 PM8/28/02
to
Hey All, I am having some trobule migrating my application from WAS
3.5.4 to WAS 4.0.1 on Windows 2000. The adminserver does not come up
and I get a server specific error 10. Please help...
Seems lke I am having trouble with the DB2 driver.
I am running DB2 7.1.6 (essentially DB2 7.3)
I am using JDBC 2.0 (I did check the inuse file in the java12
directory)
One thing to mention is that the WAS database is on a remote server
that is also
running DB2 7.1.6.
Here is an extract from the error file....

AdminServer X WSVR0009E: Error occurred during startup
java.lang.IllegalAccessError: try to access field
COM/ibm/db2/jdbc/app/DB2Driver.loaded from class
COM/ibm/db2/jdbc/DB2BaseDataSource
at COM.ibm.db2.jdbc.DB2BaseDataSource.isLoaded(DB2BaseDataSource.java:354)
at COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource.getPooledConnection(DB2ConnectionPoolDataSource.java:102)
at com.ibm.ejs.cm.pool.JDBC1xConnectionFactory.createConnection(JDBC1xConnectionFactory.java:42)
at com.ibm.ejs.cm.pool.ConnectionPool.createConnection(ConnectionPool.java:914)
at com.ibm.ejs.cm.pool.ConnectionPool.createOrWaitForConnection(ConnectionPool.java:846)
at com.ibm.ejs.cm.pool.ConnectionPool.findFreeConnection(ConnectionPool.java:764)
at com.ibm.ejs.cm.pool.ConnectionPool.findConnectionForTx(ConnectionPool.java:676)
at com.ibm.ejs.cm.pool.ConnectionPool.allocateConnection(ConnectionPool.java:610)
at com.ibm.ejs.cm.pool.ConnectionPool.getConnection(ConnectionPool.java:274)
at com.ibm.ejs.cm.pool.ConnectionPool.getConnection(ConnectionPool.java:269)
at com.ibm.ejs.cm.DataSourceImpl.getConnection(DataSourceImpl.java:99)
at com.ibm.ejs.sm.util.db.DBMgr.initialize(DBMgr.java:206)
at com.ibm.ejs.sm.server.AdminServer.initializeConnectionManager(AdminServer.java:1135)
at com.ibm.ws.runtime.Server.initializeRuntime0(Server.java:943)
at com.ibm.ejs.sm.server.ManagedServer.initializeRuntime0(ManagedServer.java:407)
at com.ibm.ejs.sm.server.AdminServer.initializeRuntime0(AdminServer.java:1104)
at com.ibm.ws.runtime.Server.initializeRuntime(Server.java:882)
at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:391)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:158)

[02.08.28 13:52:41:125 CDT] 151ecd24 AdminServer F WSVR0067E: Failed
to initialize WebSphere Administration server

Thank you all,
Shalini

Ranjit Nayak

unread,
Aug 29, 2002, 12:52:42 PM8/29/02
to
Since the errors are related to the admin server and not your
application, first ensure that WAS 4.0.1 is installed and tested.

I hope you are not pointing the the same admin database as WAS 3.5.
was pointing to.

- Ranjit


sha...@austin.rr.com (shalini) wrote in message news:<274a972b.02082...@posting.google.com>...

shalini

unread,
Sep 5, 2002, 1:02:59 PM9/5/02
to
I am pointing to a WAS 40 database. The error occurred because the
remote server that hosted the WA 40 database was not running JDBC 2.0.

Thanks!
Shalini

ranjit...@yahoo.com (Ranjit Nayak) wrote in message news:<16d93eba.02082...@posting.google.com>...

0 new messages