Problem using Microsoft SQL Server 2000 JDBC Driver
 Technote (troubleshooting)
 
Problem(Abstract)
When using the Microsoft® SQL Server 2000 JDBC Driver, the Test Connection for the data source works; however, the application accessing the data source fails with the error message, J2CA0036E and J2CA0009E.
 
Cause
The problem occurs only when WAS.database trace is enabled. Disable WAS.database to fix the error. This is due to certain versions of the Microsoft driver not including the expected debug classes.

Excerpt of the stack trace
8/6/04 15:31:02:346 EDT] 6ad55e63 ConnectionFac E J2CA0036E: An exception occurred while invoking method setDataSourceProperties on com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl used by resource jdbc/MSSQLDS : java.lang.reflect.InvocationTargetException: java.lang.NoClassDefFoundError: com/merant/jdbcspy/SpyLogger
at
com.microsoft.jdbcx.base.BaseDataSource.setLogWriter(Unknown Source)

at
com.ibm.ws.rsadapter.spi.WSRdbDataSource.setLogWriter(WSRdbDataSource.java:612)

at
com.ibm.ws.rsadapter.spi.InternalGenericDataStoreHelper.setupInitialJDBCTraceIfNecessary(InternalGenericDataStoreHelper.java:202)

at
com.ibm.ws.rsadapter.spi.WSRdbDataSource.<init>(WSRdbDataSource.java:352)

....
...
[8/6/04 15:31:02:406 EDT] 6ad55e63 ConnectionFac E J2CA0009E: An exception occurred while trying to instantiate the ManagedConnectionFactory class com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl used by resource jdbc/MSSQLDS : java.lang.reflect.InvocationTargetException: java.lang.NoClassDefFoundError: com/merant/jdbcspy/SpyLogger
at
com.microsoft.jdbcx.base.BaseDataSource.setLogWriter(Unknown Source)

at
com.ibm.ws.rsadapter.spi.WSRdbDataSource.setLogWriter(WSRdbDataSource.java:612)

at
com.ibm.ws.rsadapter.spi.InternalGenericDataStoreHelper.setupInitialJDBCTraceIfNecessary(InternalGenericDataStoreHelper.java:202)

 
Resolving the problem
To verify if the WAS.database trace is enabled, perform the following steps:
  1. Open the administrative console.

  2. Navigate to Troubleshooting > Logs and Trace > server_name > Diagnostic Trace.

  3. In the Configuration tab, under General Properties, make sure either the checkbox, Enable trace with the following specification is cleared, or that the field Trace Specification does not contain either of the following:

    *=all=enabled

    OR

    WAS.database=enabled

    If trace is needed, specify the required trace components. Do not specify:

    *=all=enabled
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > DB Connections/Connection Pooling
Operating system(s): Windows
Software version: 6.1
Software edition:
Reference #: 1176724
IBM Group: Software Group
Modified date: Aug 16, 2004