Caused by: com.sybase.jdbc3.utils.UnimplementedOperationException: The method com.sybase.jdbc3.jdbc.SybConnectionProxy.getHoldability() has not been completed and should not be called.
at com.sybase.jdbc3.jdbc.ErrorMessage.raiseRuntimeException(Unknown Source)
at com.sybase.jdbc3.utils.Debug.notImplemented(Unknown Source)
at com.sybase.jdbc3.jdbc.SybConnectionProxy.getHoldability(Unknown Source)
======================
[7/24/06 16:30:52:165 EDT] 0000002e SystemOut O === jdbc/sybds1
[7/24/06 16:30:52:602 EDT] 0000002e ConnectionFac W J2CA0294W: Deprecated usage of direct JNDI lookup of resource jdbc/sybds1. The following default values are used: [Resource-ref settings]
res-auth: 1 (APPLICATION)
res-isolation-level: 0 (TRANSACTION_NONE)
res-sharing-scope: true (SHAREABLE)
loginConfigurationName: null
loginConfigProperties: null
[Other attributes]
res-resolution-control: 999 (undefined)
isCMP1_x: false (not CMP1.x)
isJMS: false (not JMS)
[7/24/06 16:30:53:351 EDT] 0000002e WSRdbDataSour I DSRA8203I: Database product name : Adaptive Server Enterprise
[7/24/06 16:30:53:367 EDT] 0000002e WSRdbDataSour I DSRA8204I: Database product version : Adaptive Server Enterprise/12.5.0.1/EBF 10430 ESD#2/P/NT (IX86)/OS 4.0/rel12501/1/32-bit/OPT/Tue Jul 30 23:45:57 2002
[7/24/06 16:30:53:367 EDT] 0000002e WSRdbDataSour I DSRA8205I: JDBC driver name : jConnect (TM) for JDBC (TM)
[7/24/06 16:30:53:398 EDT] 0000002e WSRdbDataSour I DSRA8206I: JDBC driver version : jConnect (TM) for JDBC(TM)/6.05(Build 25828)/P/EBF13044/DEBUG/JDK14/Fri Sep 30 1:01:01 2005
[7/24/06 16:30:53:476 EDT] 0000002e FreePool E J2CA0046E: Method createManagedConnectionWithMCWrapper caught an exception during creation of the ManagedConnection for resource jdbc/sybds1, throwing ResourceAllocationException. Original exception: com.sybase.jdbc3.utils.UnimplementedOperationException: The method com.sybase.jdbc3.jdbc.SybConnectionProxy.getHoldability() has not been completed and should not be called.
at com.sybase.jdbc3.jdbc.ErrorMessage.raiseRuntimeException(Unknown Source)
at com.sybase.jdbc3.utils.Debug.notImplemented(Unknown Source)
at com.sybase.jdbc3.jdbc.SybConnectionProxy.getHoldability(Unknown Source)
at com.ibm.ws.rsadapter.spi.InternalGenericDataStoreHelper.getHoldability(InternalGenericDataStoreHelper.java:362)
at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.<init>(WSRdbManagedConnectionImpl.java:646)
at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.createManagedConnection(WSManagedConnectionFactoryImpl.java:941)
at com.ibm.ejs.j2c.poolmanager.FreePool.createManagedConnectionWithMCWrapper(FreePool.java:1502)
at com.ibm.ejs.j2c.poolmanager.FreePool.createOrWaitForConnection(FreePool.java:1294)
at com.ibm.ejs.j2c.poolmanager.PoolManager.reserve(PoolManager.java:2000)
at com.ibm.ejs.j2c.ConnectionManager.allocateMCWrapper(ConnectionManager.java:769)
at com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java:569)
at com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java:328)
at com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java:297)
at com.ibm._jsp._index._jspService(_index.java:89)
at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:88)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1212)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:629)
at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:117)
at com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java:171)
at com.ibm.ws.jsp.webcontainerext.JSPExtensionProcessor.handleRequest(JSPExtensionProcessor.java:230)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:2837)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:220)
at com.ibm.ws.webcontainer.VirtualHost.handleRequest(VirtualHost.java:204)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1681)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:77)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:421)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:367)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:276)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminaters(NewConnectionInitialReadCallback.java:201)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:103)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:548)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:601)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:934)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1021)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1332)
You may want to refer to the release notes for the JConnect for JDBC 6.05:
http://www.sybase.com/detail?id=1037380#CHDEEJAI
It appears that the method Connection.getHoldability() has been depracated.
Regards
Mayur
But I am not calling it
WAS connection pool is doing that!
Is there a feature that I can turn off, which needs that API?
Not sure your specific environmental details in terms WAS version, OS version, etc so cannot comment any further on this.
I am assuming your are using the jconn3.jar but you tried the same using the jconn2.jar and see if it makes any difference. This is just to check that the jconn3 driver is not the problem.
Let us know how get on in any case.
Regards
Mayur
Just wanted to mention that getHoldability() method is part the Connection Object in JDBC 3.0 specification. It appears that this method is not supported by the Sybase JDBC driver.
Also please refer to the following link for Cursor Holdability support:
Regards
Mayur