CWYBC0610E error with JDBC Adapter

* * * * * 1 votes

Published June 11th, 2008 in Websphere Process Server / Integration Developer

Today I was working on JDBC Adapter. I created the project and completed all the required configurations. I have created a new J2C Authentication data also. Everything looked perfect in my WebSphere Integration Developer. However when I deployed this application, I started to get the following error.

[6/12/08 14:23:40:826 IST] 00000066 ResourceAdapt E com.ibm.j2ca.jdbc.inbound.JDBCInboundDBHandler getDBConnection CWYBC0610E: The adapter failed to load the driver for the following reason: com.ibm.db2.jcc.DB2Driver.  Explanation=The adapter loads the JDBC driver and then uses it to establish a connection to the database. If the driver does not exist in the class path, the adapter returns this error.  UserAction=Make sure that the JDBC driver classes are in the class path.
[6/12/08 14:23:41:248 IST] 00000066 ResourceAdapt E com.ibm.j2ca.base.WBIResourceAdapter endpointActivation(MessageEndpointFactory,ActivationSpec) Endpoint activation failed
javax.resource.ResourceException: Failed to establish event manager
	at com.ibm.j2ca.base.WBIResourceAdapter.createEventManager(WBIResourceAdapter.java:318)
	at com.ibm.j2ca.base.WBIResourceAdapter$1.createEventManager(WBIResourceAdapter.java:184)
	at com.ibm.j2ca.base.internal.EndpointManager.startPolling(EndpointManager.java:190)
	at com.ibm.j2ca.base.internal.EndpointManager.addEndpoint(EndpointManager.java:134)
	at com.ibm.j2ca.base.WBIResourceAdapter.endpointActivation(WBIResourceAdapter.java:252)
	at com.ibm.ejs.j2c.ActivationSpecWrapperImpl.activateEndpoint(ActivationSpecWrapperImpl.java:299)
	at com.ibm.ejs.j2c.RAWrapperImpl.activateEndpoint(RAWrapperImpl.java:847)
	at com.ibm.ejs.j2c.RALifeCycleManagerImpl.activateEndpoint(RALifeCycleManagerImpl.java:1371)
	at com.ibm.ejs.container.MessageEndpointFactoryImpl.activateEndpoint(MessageEndpointFactoryImpl.java:256)
	at com.ibm.ws.runtime.component.EJBContainerImpl.install(EJBContainerImpl.java:2886)
	at com.ibm.ws.runtime.component.EJBContainerImpl.start(EJBContainerImpl.java:3548)
	at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1245)
	at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1067)
	at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:547)

The fix for this issue was relatively easy for me. The issue was, the DB2 Driver path was not mentioned in WebSphere variables. To fix this issue, logon to admin console. Click on Environment -> WebSphere variables. Update the value for DB2UNIVERSAL_JDBC_DRIVER_NATIVEPATH, DB2UNIVERSAL_JDBC_DRIVER_PATH and DB2_JDBC_DRIVER_PATH with DB2 driver path. I don’t know whether we need to update all the three variables. But I updated it and my problem resolved.

Bookmark to