• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Correct JDBC Driver for Sybase 12.x in Websphere 6.1

 
Priyadarshan Kelkar
Ranch Hand
Posts: 31
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have configured a Sybase 12.x DataSource called 'jdbc/SybaseData' in Websphere 6.1.

The jar used is jtds-1.2.5.jar with following details:

Implementation class name: net.sourceforge.jtds.jdbcx.JtdsDataSource

Data store helper class name: com.ibm.websphere.rsadapter.ConnectJDBCDataStoreHelper


I am using quartz scheduler in my application. It gives the following exception.

[2/14/11 11:02:06:831 EST] 00000030 FreePool E J2CA0045E: Connection not available while invoking method createOrWaitForConnection for resource jdbc/SybaseData.
[2/14/11 11:02:06:834 EST] 0000002f FreePool E J2CA0045E: Connection not available while invoking method createOrWaitForConnection for resource jdbc/SybaseData.
[2/14/11 11:02:21:779 EST] 00000032 FreePool E J2CA0045E: Connection not available while invoking method createOrWaitForConnection for resource jdbc/SybaseData.
[2/14/11 11:02:21:781 EST] 00000032 ErrorLogger E org.quartz.core.ErrorLogger schedulerError An error occured while marking executed job complete (will continue attempts). job= 'DEFAULT.RateServerJob'
org.quartz.JobPersistenceException: Failed to obtain DB connection from data source 'MYDS': java.sql.SQLException: Could not retrieve datasource via JNDI url 'jdbc/SybaseData' com.ibm.websphere.ce.cm.ConnectionWaitTimeoutException: Connection not available, Timed out waiting for 180028 [See nested exception: java.sql.SQLException: Could not retrieve datasource via JNDI url 'jdbc/SybaseData' com.ibm.websphere.ce.cm.ConnectionWaitTimeoutException: Connection not available, Timed out waiting for 180028]
at org.quartz.impl.jdbcjobstore.JobStoreSupport.getConnection(JobStoreSupport.java:690)
at org.quartz.impl.jdbcjobstore.JobStoreTX.getNonManagedTXConnection(JobStoreTX.java:69)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3753)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3725)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.triggeredJobComplete(JobStoreSupport.java:2957)
at org.quartz.core.QuartzScheduler.notifyJobStoreJobComplete(QuartzScheduler.java:1789)
at org.quartz.core.JobRunShell.completeTriggerRetryLoop(JobRunShell.java:416)
at org.quartz.core.JobRunShell.run(JobRunShell.java:293)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549)
Caused by: java.sql.SQLException: Could not retrieve datasource via JNDI url 'jdbc/SybaseData' com.ibm.websphere.ce.cm.ConnectionWaitTimeoutException: Connection not available, Timed out waiting for 180028
at org.quartz.utils.JNDIConnectionProvider.getConnection(JNDIConnectionProvider.java:163)
at org.quartz.utils.DBConnectionManager.getConnection(DBConnectionManager.java:109)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.getConnection(JobStoreSupport.java:687)
... 8 more

[2/14/11 11:02:26:539 EST] 0000003f FreePool E J2CA0045E: Connection not available while invoking method createOrWaitForConnection for resource jdbc/SybaseData.
[2/14/11 11:02:26:571 EST] 00000040 FreePool E J2CA0045E: Connection not available while invoking method createOrWaitForConnection for resource jdbc/SybaseData.
[2/14/11 11:02:44:682 EST] 0000003e FreePool E J2CA0045E: Connection not available while invoking method createOrWaitForConnection for resource jdbc/SybaseData.
[2/14/11 11:02:53:749 EST] 0000002d FreePool E J2CA0045E: Connection not available while invoking method createOrWaitForConnection for resource jdbc/SybaseData.


Will be happy to provide any more information required.
Please help me ..... this is urgent ...
Thanks !
 
aishwarya piramana
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
How did you fix this issue?? Any updates.. please. Am also stuck with the same issue
 
Priyadarshan Kelkar
Ranch Hand
Posts: 31
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I used JTA transaction in my Spring configuration instead of Datasource transaction and the issue was resolved.
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic