Method cleanup failed while trying to execute method cleanup on ManagedConnection

[Scott Herter]

I am using SQL Server 2005 standard edition. Here is the version
information in the logs

Database product version : 9.00.2153
JDBC driver name : Microsoft SQL Server 2005 JDBC Driver
JDBC driver version : 1.1.1501.101

We are connecting using the XA data source for pooling through IBM WebSphere
Application Server 5.1.1.10. Our application seems to be working fine but
every time a connection is closed we get a stack trace in the log indicating
that destroy failed and that a method is not supportd with "Caused by:
java.sql.SQLException: This operation is not supported.DSRA0010E: SQL State
= null, Error Code = 0". I have tried searching for SQL Stat = null, Error
code = 0 and gotten no hits. We have used the same set up but using the SQL
Server 2000 JDBC driver talking to a SQL Server 2000 database without a
problem, the only difference is we switched it to use SQL Server 2005. Does
anybody know what could be causing this? Is there some change we need to
make to our code that 2005 needs that worked with 2000?

Thanks.

Here is a full stack trace:
[11/3/06 9:44:27:201 CST] 73c1b42d WSRdbManagedC E DSRA0010E: SQL State =
<null>, Error Code = 0
[11/3/06 9:44:27:232 CST] 73c1b42d MCWrapper E J2CA0081E: Method cleanup
failed while trying to execute method cleanup on ManagedConnection
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl@23027409 from resource
jdbc/SQL2005Repository. Caught exception: com.ibm.ws.exception.WsException:
DSRA0080E: An exception was received by the Data Store Adapter. See original
exception message: This operation is not supported.. with SQL State : null
SQL Code : 0
at
com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(Unknown
Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.NotImplemented(Unknown
Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.setTypeMap(Unknown
Source)
at
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.setTypeMap(WSRdbManagedConnectionImpl.java:3373)
at
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanupStates(WSRdbManagedConnectionImpl.java:2528)
at
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanup(WSRdbManagedConnectionImpl.java:2396)
at com.ibm.ejs.j2c.MCWrapper.cleanup(MCWrapper.java:1195)
at com.ibm.ejs.j2c.poolmanager.FreePool.returnToFreePool(FreePool.java:329)
at com.ibm.ejs.j2c.poolmanager.PoolManager.release(PoolManager.java:1311)
at com.ibm.ejs.j2c.MCWrapper.releaseToPoolManager(MCWrapper.java:1777)
at
com.ibm.ejs.j2c.LocalTransactionWrapper.afterCompletionCode(LocalTransactionWrapper.java:1092)
at
com.ibm.ejs.j2c.LocalTransactionWrapper.afterCompletion(LocalTransactionWrapper.java:1026)
at
com.ibm.ws.LocalTransaction.LocalTranCoordImpl.informSynchronizations(LocalTranCoordImpl.java:1313)
at
com.ibm.ws.LocalTransaction.LocalTranCoordImpl.cleanup(LocalTranCoordImpl.java:1038)
at
com.ibm.ws.webcontainer.webapp.WebAppTransactionCollaborator.postInvoke(WebAppTransactionCollaborator.java:249)
at
com.ibm.ws.webcontainer.webapp.WebAppServletManager.addServlet(WebAppServletManager.java:891)
at
com.ibm.ws.webcontainer.webapp.WebAppServletManager.loadServlet(WebAppServletManager.java:224)
at
com.ibm.ws.webcontainer.webapp.WebAppServletManager.loadAutoLoadServlets(WebAppServletManager.java:542)
at
com.ibm.ws.webcontainer.webapp.WebApp.loadServletManager(WebApp.java:1379)
at com.ibm.ws.webcontainer.webapp.WebApp.init(WebApp.java:292)
at com.ibm.ws.webcontainer.srt.WebGroup.loadWebApp(WebGroup.java:408)
at com.ibm.ws.webcontainer.srt.WebGroup.init(WebGroup.java:212)
at
com.ibm.ws.webcontainer.WebContainer.addWebApplication(WebContainer.java:1012)
at
com.ibm.ws.runtime.component.WebContainerImpl.install(WebContainerImpl.java:136)
at
com.ibm.ws.runtime.component.WebContainerImpl.start(WebContainerImpl.java:356)
at
com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:517)
at
com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:808)
at
com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:354)
at
com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:578)
at
com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:311)
at
com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:268)
at
com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at
com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:152)
at
com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:246)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:222)
at java.lang.Thread.run(Thread.java:567)
Caused by: java.sql.SQLException: This operation is not supported.DSRA0010E:
SQL State = null, Error Code = 0
... 46 more
---- Begin backtrace for nested exception
java.sql.SQLException: This operation is not supported.DSRA0010E: SQL State
= null, Error Code = 0
at
com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(Unknown
Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.NotImplemented(Unknown
Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.setTypeMap(Unknown
Source)
at
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.setTypeMap(WSRdbManagedConnectionImpl.java:3373)
at
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanupStates(WSRdbManagedConnectionImpl.java:2528)
at
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanup(WSRdbManagedConnectionImpl.java:2396)
at com.ibm.ejs.j2c.MCWrapper.cleanup(MCWrapper.java:1195)
at com.ibm.ejs.j2c.poolmanager.FreePool.returnToFreePool(FreePool.java:329)
at com.ibm.ejs.j2c.poolmanager.PoolManager.release(PoolManager.java:1311)
at com.ibm.ejs.j2c.MCWrapper.releaseToPoolManager(MCWrapper.java:1777)
at
com.ibm.ejs.j2c.LocalTransactionWrapper.afterCompletionCode(LocalTransactionWrapper.java:1092)
at
com.ibm.ejs.j2c.LocalTransactionWrapper.afterCompletion(LocalTransactionWrapper.java:1026)
at
com.ibm.ws.LocalTransaction.LocalTranCoordImpl.informSynchronizations(LocalTranCoordImpl.java:1313)
at
com.ibm.ws.LocalTransaction.LocalTranCoordImpl.cleanup(LocalTranCoordImpl.java:1038)
at
com.ibm.ws.webcontainer.webapp.WebAppTransactionCollaborator.postInvoke(WebAppTransactionCollaborator.java:249)
at
com.ibm.ws.webcontainer.webapp.WebAppServletManager.addServlet(WebAppServletManager.java:891)
at
com.ibm.ws.webcontainer.webapp.WebAppServletManager.loadServlet(WebAppServletManager.java:224)
at
com.ibm.ws.webcontainer.webapp.WebAppServletManager.loadAutoLoadServlets(WebAppServletManager.java:542)
at
com.ibm.ws.webcontainer.webapp.WebApp.loadServletManager(WebApp.java:1379)
at com.ibm.ws.webcontainer.webapp.WebApp.init(WebApp.java:292)
at com.ibm.ws.webcontainer.srt.WebGroup.loadWebApp(WebGroup.java:408)
at com.ibm.ws.webcontainer.srt.WebGroup.init(WebGroup.java:212)
at
com.ibm.ws.webcontainer.WebContainer.addWebApplication(WebContainer.java:1012)
at
com.ibm.ws.runtime.component.WebContainerImpl.install(WebContainerImpl.java:136)
at
com.ibm.ws.runtime.component.WebContainerImpl.start(WebContainerImpl.java:356)
at
com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:517)
at
com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:808)
at
com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:354)
at
com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:578)
at
com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:311)
at
com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:268)
at
com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at
com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:152)
at
com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:246)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:222)
at java.lang.Thread.run(Thread.java:567)

[Joe Weinstein]

Scott Herter wrote:

> I am using SQL Server 2005 standard edition. Here is the version
> information in the logs
>
> Database product version : 9.00.2153
> JDBC driver name : Microsoft SQL Server 2005 JDBC Driver
> JDBC driver version : 1.1.1501.101
>
> We are connecting using the XA data source for pooling through IBM WebSphere
> Application Server 5.1.1.10. Our application seems to be working fine but
> every time a connection is closed we get a stack trace in the log indicating
> that destroy failed and that a method is not supportd with "Caused by:
> java.sql.SQLException: This operation is not supported.DSRA0010E: SQL State
> = null, Error Code = 0". I have tried searching for SQL Stat = null, Error
> code = 0 and gotten no hits. We have used the same set up but using the SQL
> Server 2000 JDBC driver talking to a SQL Server 2000 database without a
> problem, the only difference is we switched it to use SQL Server 2005. Does
> anybody know what could be causing this? Is there some change we need to
> make to our code that 2005 needs that worked with 2000?
>
> Thanks.

Hi. It's a bug in the driver. WebSphere could do a better job too though...
The WebSphere pool code is trying to make sure a connection is in it's
default state for the next user. Presumably it called Connection.getTypeMap()
before giving it to user code, and now that the connection is back from
user code, the pool is resetting the type map to the default, in case your
code had changed it.
I verified that the MS driver's getTypeMap() works fine, returning an
empty Map, but c.setTypeMap( c.getTypeMap() ) fails with the exception
you're getting. The driver should at least accept it's own default type
map, but WebSphere could do better to detect when a connection state-
changing call was made by user code, and only do the reset calls that
were actually needed in a particular case.

Joe Weinstein at BEA Systems.

[Scott Herter]

Thanks for the information. I was afraid I was going to have to go through
all the code to make some tweak everytime a connection was used.

"Joe Weinstein" <joeN...@bea.com> wrote in message
news:454B8463...@bea.com...

[Goerlitz [MSFT]@discussions.microsoft.com Shelby Goerlitz [MSFT]]

Scott:

This is a known issue and is scheduled to be addressed in our next driver
release.

-shelby

Shelby Goerlitz
Microsoft SQL Server Data Programmability

[vedat]

Scott Herter wrote on 11/03/2006 12:45 ET :
> I am using SQL Server 2005 standard edition. Here is the version
> information in the logs
>
> Database product version : 9.00.2153
> JDBC driver name : Microsoft SQL Server 2005 JDBC Driver
> JDBC driver version : 1.1.1501.101
>
> We are connecting using the XA data source for pooling through IBM WebSphere
> Application Server 5.1.1.10. Our application seems to be working fine but
> every time a connection is closed we get a stack trace in the log indicating
> that destroy failed and that a method is not supportd with "Caused by:
> java.sql.SQLException: This operation is not supported.DSRA0010E: SQL State
> = null, Error Code = 0". I have tried searching for SQL Stat = null,
> Error
> code = 0 and gotten no hits. We have used the same set up but using the SQL
> Server 2000 JDBC driver talking to a SQL Server 2000 database without a
> problem, the only difference is we switched it to use SQL Server 2005. Does
> anybody know what could be causing this? Is there some change we need to
> make to our code that 2005 needs that worked with 2000?
>
> Thanks.
>
> Here is a full stack trace:
> [11/3/06 9:44:27:201 CST] 73c1b42d WSRdbManagedC E DSRA0010E: SQL State =
> <null>, Error Code = 0
> [11/3/06 9:44:27:232 CST] 73c1b42d MCWrapper E J2CA0081E: Method cleanup
> failed while trying to execute method cleanup on ManagedConnection

hi;

at which version does it fixed ?