Hello All, I have been fighting a very annoying bug in WTE( Websphere Test Environment) which is part of VAJ3.5. Yes! Unfortunately my company is still in WAS3.5 days and we have not migrated to WAS4.0 yet. All was working fine in VAJ till a couple of days ago. All of a sudden, when I start my WTE, the servlet engine fails to load the db2 driver. I have tried all kinds of things but it SIMPLY REFUSES TO GO AWAY!. Could anybody please shed some light on this?. or Have anybody else experienced the same problem?. I am listing below the exact stack trace : STACK TRACE: *********** #ERROR#: Error retrieving connectionException:Error loading JDBC driver: COM.ibm.db2.jdbc.app.DB2Driver #ERROR#: START STACK TRACE java.sql.SQLException: Error loading JDBC driver: COM.ibm.db2.jdbc.app.DB2Driver java.lang.Throwable(java.lang.String) java.lang.Exception(java.lang.String) java.sql.SQLException(java.lang.String) java.sql.Driver com.ibm.ejs.cm.JDBCDataSource.loadAndCheckDriver() com.ibm.ejs.cm.pool.ConnectionFactory com.ibm.ejs.cm.JDBCDataSource.createConnectionFactory() javax.sql.DataSource com.ibm.ejs.cm.DataSourceImpl.getSource() java.sql.Connection com.ibm.ejs.cm.DataSourceImpl.getConnection(java.lang.String, java.lang.String) java.sql.Connection com.tuc.database.ConnectionPool.getConnection(java.lang.String, java.lang.String) com.tuc.database.ScoresDatabase() void com.tuc.servlets.MediatorServlet.init(javax.servlet.ServletConfig) void com.ibm.servlet.engine.webapp.StrictServletInstance.doInit() void com.ibm.servlet.engine.webapp.StrictLifecycleServlet._init(javax.servlet.ServletConfig) void com.ibm.servlet.engine.webapp.PreInitializedServletState.init(com.ibm.servlet.engine.webapp.StrictLifecycleServlet, javax.servlet.ServletConfig) void com.ibm.servlet.engine.webapp.StrictLifecycleServlet.init(javax.servlet.ServletConfig) void com.ibm.servlet.engine.webapp.ServletInstance.init() void javax.servlet.GenericServlet.init(javax.servlet.ServletConfig) void com.ibm.servlet.engine.webapp.ServletManager.addServlet(java.lang.String, javax.servlet.Servlet, java.util.Properties) void com.ibm.servlet.engine.webapp.WebAppServletManager.loadServlet(java.lang.String) void com.ibm.servlet.engine.webapp.WebAppServletManager.loadAutoLoadServlets() void com.ibm.servlet.engine.webapp.WebApp.loadServletManager() void com.ibm.servlet.engine.webapp.WebApp.init(com.ibm.servlet.engine.config.WebAppInfo, com.ibm.servlet.engine.webapp.WebAppContext) void com.ibm.servlet.engine.srt.WebGroup.loadWebApp() void com.ibm.servlet.engine.srt.WebGroup.init(com.ibm.servlet.engine.ServletHost, com.ibm.servlet.engine.config.WebGroupInfo) void com.ibm.servlet.engine.ServletHost.loadWebGroups() void com.ibm.servlet.engine.ServletHost.init(com.ibm.servlet.engine.ServletEngine, com.ibm.servlet.engine.config.ServletHostInfo) void com.ibm.servlet.engine.ServletEngine.loadServletHosts() void com.ibm.servlet.engine.ServletEngine.init(com.ibm.servlet.engine.config.ServletEngineInfo) com.ibm.servlet.engine.ServletEngine com.ibm.servlet.engine.ServletEngine.getEngine() void com.ibm.ivj.control.node.ServletEngineRunner.restartServletEngine(boolean) void com.ibm.ivj.control.node.ServletEngineRunner$RestartServletEngineThread.run()
SOLUTION 1: ********** It was posted in the javaranch a while back. a.) close VAJ b.) Rename the db2driver.zip to something else. C.) Bring up VAJ. d.) Rename the db2driver.zip back to its original name e.) start WTE THIS DIDN'T WORK! SOLUTION 2: ********** Reinstall VAJ 3.5. THIS DIDN'T WORK! SOLUTION 3: ********** May be the db2 driver was bad. So I replaced it THIS DIDN'T WORK! aLL Classpaths are pointing to the right db2driver.zip. Thanks Sudharsan
0
