JDBC driver not found during startup
If you are using a database or property extension repository, the problem described here might occur when you start WebSphere Application Server.
Problem
A ClassNotFoundException occurs as shown in this sample virtual member manager trace:
Caused by: java.lang.ClassNotFoundException: com.ibm.db2.jcc.DB2Driver
at java.lang.Class.forNameImpl(Native Method)
at java.lang.Class.forName(Class.java:163)
at com.ibm.ws.wim.dao.AbstractDAO.loadJDBCClass(AbstractDAO.java:300)
(If you are using WebSphere Application Server version 6.1, you may get the following exception which is confusing: The registry implementation file com.ibm.ws.wim.registry.WIMUserRegistry cannot be initialized because of the following exception com.ibm.websphere.wim.exception.WIMConfigurationException: CWWIM5034E The parameter value 'uid' is not correct for the parameter 'loginProperties'. The parameter must have one of the following values: 'null' . Install the WebSphere Application Server 6.1.0.19 fix pack to replace the ambiguous exception with the root case ClassNotFoundException.)
Solution
Copy the JDBC driver(s) to app_server_root/lib directory and restart the server.