WAS admin server is not getting started after installation on window 2000 server, service specific error 10.
I've installed WebSphere app server v4.0.1 on a windows 2000 server with the following environment
I tried this installation according to the redbook WAS4.0 Handbook
OS: Windows 2000 Server with Service pack 3.0
WAS : WAS 4.0.1 with NO Fixpacks applied
Admin server repository on a remote windows 2000 professional machine with DB2 UDB v7.2 with NO Fixpacks
I've updated the
JDBC driver at both the db2 server and client(The was server) machines using usejdbc2.bat
I did create the admin database and configure it in the admin client installed on the app server machine.
The user name is db2admin with password db2admin and it has got all the rights and I'm able to connect to the admin server database (I named it as was1) using this uid and pswd both locally and from the remote machine where websphere is installed.
while installing WAS i opted for remote database and i gave the server host ip, port number as 50000 and the path of the SQLLIB folder in the db2 server machine also. Every thing went fine till the installation, but there after the admin
server is not coming up. Its saying service startup failed 'service specific error 10'
Since the admin db is already created, I renamed the createwasdb.scr to createwasdb.bak and so an error msg was logged in the wasdb2.log file saying that file is not found.
I checked the log files and trace files.
The following is what I could find in the file __adminServerFatalError1041291831781.log
[02.12.30 18:43:51:796 EST] 14acec45 SharedLogWrit prepare entry
[02.12.30 18:43:51:812 EST] 14acec45 SharedLogWrit prepare entry
[02.12.30 18:43:51:812 EST] 14acec45 SharedLogWrit writeDataAndHeader
[02.12.30 18:43:51:812 EST] 14acec45 SharedLogWrit D writeDataAndHeader - writing 2499 bytes to location 79030
[02.12.30 18:43:51:812 EST] 14acec45 SharedLogWrit D writeDataAndHeader - write complete, filePointer = 81529
[02.12.30 18:43:51:828 EST] 14acec45 SharedLogWrit D writeDataAndHeader - freeSpace ptr = 81529
[02.12.30 18:43:51:828 EST] 14acec45 SharedLogWrit writeDataAndHeader
[02.12.30 18:43:51:828 EST] 14acec45 TraceNLS D TraceNLS instance doesn't exist for
com.ibm.ejs.resources.seriousMessages
[02.12.30 18:43:51:828 EST] 14acec45 TraceNLS D Bundle not cached for name com.ibm.ejs.resources.seriousMessages
[02.12.30 18:43:51:843 EST] 14acec45 TraceNLS D Loaded ResourceBundle com.ibm.ejs.resources.seriousMessages
[02.12.30 18:43:51:781 EST] 14acec45 DBMgr F SMTL0026E: Failure to create a data source:
COM.ibm.db2.jdbc.DB2Exception: [IBM][JDBC Driver] CLI0615E Error receiving from socket, server is not responding.
SQLSTATE=08S01
at COM.ibm.db2.jdbc.net.SQLExceptionGenerator.throwReceiveError(SQLExceptionGenerator.java:457)
at COM.ibm.db2.jdbc.net.DB2Request.receive(DB2Request.java:703)
at COM.ibm.db2.jdbc.net.DB2Request.sendAndRecv(DB2Request.java:563)
at COM.ibm.db2.jdbc.net.DB2Connection.SQLConnect(DB2Connection.java:341)
at COM.ibm.db2.jdbc.net.DB2Connection.SQLConnect(DB2Connection.java:296)
at COM.ibm.db2.jdbc.net.DB2Connection.create(DB2Connection.java:281)
at COM.ibm.db2.jdbc.net.DB2Connection.init(DB2Connection.java:191)
at COM.ibm.db2.jdbc.net.DB2ReusableConnection.init(DB2ReusableConnection.java:69)
at COM.ibm.db2.jdbc.DB2PooledConnection.getConnection(DB2PooledConnection.java:201)
at com.ibm.ejs.cm.pool.ConnectO.<init>(ConnectO.java:85)
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)
The trace file said
[02.12.30 18:43:51:968 EST] 14acec45 SystemOut U SMTL0026E: Failure to create a data source:
COM.ibm.db2.jdbc.DB2Exception: [IBM][JDBC Driver] CLI0615E Error receiving from socket, server is not responding.
SQLSTATE=08S01
at COM.ibm.db2.jdbc.net.SQLExceptionGenerator.throwReceiveError(SQLExceptionGenerator.java:457)
at COM.ibm.db2.jdbc.net.DB2Request.receive(DB2Request.java:703)
at COM.ibm.db2.jdbc.net.DB2Request.sendAndRecv(DB2Request.java:563)
at COM.ibm.db2.jdbc.net.DB2Connection.SQLConnect(DB2Connection.java:341)
at COM.ibm.db2.jdbc.net.DB2Connection.SQLConnect(DB2Connection.java:296)
at COM.ibm.db2.jdbc.net.DB2Connection.create(DB2Connection.java:281)
at COM.ibm.db2.jdbc.net.DB2Connection.<init>(DB2Connection.java:191)
at COM.ibm.db2.jdbc.net.DB2ReusableConnection.<init>(DB2ReusableConnection.java:69)
at COM.ibm.db2.jdbc.DB2PooledConnection.getConnection(DB2PooledConnection.java:201)
at com.ibm.ejs.cm.pool.ConnectO.<init>(ConnectO.java:85)
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)
The CheckloadClass.log file says Successfully loaded class COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource
wssetup.log has the following entry
DB2 is not installed on the system or the current version of DB2 does not meet the level required by this product. .
but if I'm right its not harmful, coz it was shown when I selected the default SQLLIB folder for admin repository, but got solved when i gave the remote sqllib path
I'm using db2 v7.2 with out any fixpacks.
The internal release no is "DB2 v7.1.0.40" where as the pre-req says "DB2 v7.1.0.43" is needed with fixpack 4
I've checked the user rights of the user connecting to the DB, updated the driver to jdbc2.0, have added one blank line at the end of admin.config and killed the java.exe processes - restarted restarted and still doing the same
With DB2 and the App server on the same machine, I've successfully installed manytimes. but this is the first time i'm trying with a remote DB.
Hope you guys will help me..
by the way, whats meant by 'GA' in the product names IBM DB2 UDB V7.2 GA..? please help
PS: I've removed the < symbol in the log entries
