Skip to main content

VBE/BES 5.2.1: Can the Name Service be configured to get avoid exception when setTransactionIsolation() is called

  • February 16, 2013
  • 0 replies
  • 0 views

Problem:

  • Product Name: VisiBroker
  • Product Version: 5.2.1
  • Product Component: Naming Service
  • Platform/OS Version: All
  • JDK/Compiler Version: All Supported JDKs

VBE/BES 5.2.1: Can the Name Service be configured to get avoid exception when setTransactionIsolation() is called?

When using an unsupported JDBC driver with the Naming Service, following exception is thrown:

java.sql.SQLException: This function is not supported
at com.sunopsis.jdbc.driver.xml.q.setTransactionIsolation(q.java)
at com.inprise.vbroker.naming.JDBCConnection.createTables(JDBCConnection.java:410)
at com.inprise.vbroker.naming.JDBCConnection.createOrMigrate(JDBCConnection.java:299)
at com.inprise.vbroker.naming.JDBCConnection.(JDBCConnection.java:172)
at com.inprise.vbroker.naming.JDBCFactory.(JDBCFactory.java:47)
at com.inprise.vbroker.naming.FactoryBuilder.(FactoryBuilder.java:108)
at com.inprise.vbroker.naming.FactoryBuilder.(FactoryBuilder.java:36)
at com.inprise.vbroker.naming.ExtFactory.main(ExtFactory.java:129)
00000010,12/16/03 5:10 00011684,VBJ-Application,main,ERR,JDBC,Connection.createTables: FATAL Error - Error creating tablesjava.sql.SQLException: This function is not supported

Can the Name Service be configured to avoid making the call: setTransactionIsolation(...), in order to avoid the exception?

Resolution:

Per the documentation, the following JDBC drivers that are supported by BES 5.2.1 VisiNaming:

  • com.borland.datastore.jdbc.DataStoreDriver
  • com.sybase.jdbc.SybDriver
  • oracle.jdbc.driver.OracleDriver
  • interbase.interclient.Driver
  • weblogic.jdbc.mssqlserver4.Driver
  • COM.ibm.db2.jdbc.app.DB2Driver

The officially supported databases and JDBC drivers are listed in the documentation and they have been tested and certified by our QA. So using any other databases and JDBC drivers may result in unexpected behavior. Although all of them claim to be JDBC compliant, there may be slight differences in behavior and need to be thoroughly tested. Such enhancement request may need to go through the Product Manager and be reviewed carefully.

Please be advised to only use the officially supported databases and JDBC drivers.


Author:Henry Hwang
Support Case:542537

Old KB# 26451

#VisiBroker
#NamingService
#Security