setting the isolation level for sybase datasource

[Raju]

Please help me in understnding this problem.
I have created a datasource in websphere successfully and
tested teh connection from console. I have used
com.sybase.jdbc2.jdbc.SybConnectionPoolDataSource cclass.
But when I try to get the connection from the Datasource
object, I'm getting the following error.

Plese let me know if any of you faced similor problem.

com.sybase.jdbc2.jdbc.SybSQLException: Invalid isolation
level specified.

at com.sybase.jdbc2.tds.Tds.processEed(Tds.java:3178)
at com.sybase.jdbc2.tds.Tds.nextResult(Tds.java:2481)
at
com.sybase.jdbc2.jdbc.ResultGetter.nextResult(ResultGetter.java:69)
at
com.sybase.jdbc2.jdbc.SybStatement.nextResult(SybStatement.java:220)
at
com.sybase.jdbc2.jdbc.SybStatement.nextResult(SybStatement.java:203)
at
com.sybase.jdbc2.jdbc.SybStatement.updateLoop(SybStatement.java:1717)
at
com.sybase.jdbc2.jdbc.SybStatement.executeUpdate(SybStatement.java:1700)
at
com.sybase.jdbc2.jdbc.SybPreparedStatement.executeUpdate(SybPreparedStatement.java:115)
at com.sybase.jdbc2.tds.Tds.setOption(Tds.java:1404)
at
com.sybase.jdbc2.jdbc.SybConnection.setTransactionIsolation(SybConnection.java:1358)
at
com.sybase.jdbc2.jdbc.SybConnectionProxy.setTransactionIsolation(SybConnectionProxy.java:579)
at
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.setTransactionIsolation(WSRdbManagedConnectionImpl.java:2757)
at
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.synchronizePropertiesWithCRI(WSRdbManagedConnectionImpl.java:1388)
at
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.<init>(WSRdbManagedConnectionImpl.java:411)
at
com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.createManagedConnection(WSManagedConnectionFactoryImpl.java:569)
at
com.ibm.ejs.j2c.poolmanager.FreePool.createManagedConnectionWithMCWrapper(FreePool.java:1244)
at
com.ibm.ejs.j2c.poolmanager.FreePool.createOrWaitForConnection(FreePool.java:1030)
at
com.ibm.ejs.j2c.poolmanager.PoolManager.reserve(PoolManager.java:1590)
at
com.ibm.ejs.j2c.ConnectionManager.allocateMCWrapper(ConnectionManager.java:658)
at
com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java:446)
at
com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java:215)
at
com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java:190)
at
org.apache.jsp._DataSourceTest._jspService(_DataSourceTest.java:163)
at
com.ibm.ws.webcontainer.jsp.runtime.HttpJspBase.service(HttpJspBase.java:89)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled
Code))
at
com.ibm.ws.webcontainer.jsp.servlet.JspServlet$JspServletWrapper.service(JspServlet.java(Compiled
Code))
at
com.ibm.ws.webcontainer.jsp.servlet.JspServlet.serviceJspFile(JspServlet.java:675)
at
com.ibm.ws.webcontainer.jsp.servlet.JspServlet.service(JspServlet.java:773)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled
Code))
at
com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
at
com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
at
com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
at
com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
at
com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:948)
at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java(Compiled
Code))
at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:176)
at
com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:79)
at
com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:201)
at
com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at
com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:114)
at
com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:186)
at
com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
at
com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:610)
at
com.ibm.ws.http.HttpConnection.run(HttpConnection.java:431)
at
com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled
Code))

[J]

On 12 Apr 2006 14:03:47 -0700, Raju wrote:

I would think an invalid isolation level is being specified at:
com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.setTransactionIsolation(WSRdbManagedConnectionImpl.java:2757)

For example:

1> set transaction isolation level 9
2> go
Msg 7374, Level 15, State 1:
Server 'ase125x', Line 1:
Invalid isolation level specified.

You could try to capture the values via turning on Sybase tracing with
the debug jar. or looking at the actual data traffic to the ASE to see
the proposed values.

I wonder what version of jConnect you are using. When I try this with
pretty current levels I get an error from the jConnect Api and not the
dataserver about setting the wrong value.

C:\work\Java\utils\SimpleSql\work>java SimpleSql
Hello from SimpleSql
Registered JDBC Drivers: com.sybase.jdbc2.jdbc.SybDriver@affc70
com.sybase.jdbc2.jdbc.SybConnection(Thread[main,5,main]): tryLogin()
com.sybase.jdbc2.jdbc.SybConnection(Thread[main,5,main]): hostport:
jandersxp:50
00
com.sybase.jdbc2.jdbc.SybConnection(Thread[main,5,main]):
initProtocol()
com.sybase.jdbc2.jdbc.SybConnection(Thread[main,5,main]):
getLoginTimeRemaining(
), _loginTimeout set to 0
com.sybase.jdbc2.jdbc.SybConnection(Thread[main,5,main]): init()
com.sybase.jdbc2.jdbc.SybConnection(Thread[main,5,main]):
initProtocol()
com.sybase.jdbc2.jdbc.SybConnection(Thread[main,5,main]):
getLoginTimeRemaining(
), _loginTimeout set to 0
com.sybase.jdbc2.jdbc.SybConnection(Thread[main,5,main]):
getDefaultServerCharse
t = cp850
com.sybase.jdbc2.jdbc.SybConnection(Thread[main,5,main]):
initProtocol()
com.sybase.jdbc2.jdbc.SybConnection(Thread[main,5,main]): Connection
created
doQuery: Message : JZ0I3: Incorrect argument 9 passed to method
setTransactionIs
olation.
Verify in the product documentation or in the JDBC API that the
correct argument
was passed.
doQuery: Message : JZ0I3: Incorrect argument 9 passed to method
setTransactionIs
olation.
Verify in the product documentation or in the JDBC API that the
correct argument
was passed.
com.sybase.jdbc2.jdbc.SybConnection(Thread[main,5,main]): close
com.sybase.jdbc2.jdbc.SybConnection(Thread[main,5,main]): Connection
marked DEAD
, reConnect is false

J

[nandoX]

Hello, I have the same problem, could you tell me if you
resolve this

[J]

On 8 Sep 2006 04:45:26 -0700, nandoX wrote:

The error is coming back from the dataserver. Did you install the
Metadata? You might try looking at the data traffic with Ribo utility
or specify a connection property Capture_Protocol to get the data
traffic to help isolate. What version of jConnect are you using?

Jay