Setting query timeout in TopLink 10g

Question

The 10g version of OAAM uses TopLink 10g Release 3 (10.1.3.1.0) (Build 061004) and Oracle JDBC Driver 10.2.0.2.0. We are not using TopLink Essentials. I'm trying to make it so that our queries will timeout and throw an exception if they take too long. I have tried several things, but haven't had any luck so far. I have tried each of the following:
* Adding <property name="javax.persistence.query.timeout" value="1"/> to the <login> element in sessions.xml.
* Setting the query policy in my descriptors like this:
<opm:querying xsi:type="toplink:query-policy">
<opm:timeout>1</opm:timeout>
</opm:querying>
* Calling DatabaseQuery.setQueryTimeout(1).
* Calling setProperty("javax.persistence.query.timeout") on the database login, server session, client session, and unit of work.
In each case, I tried to update a locked table, and the application simply hung until I unlocked the table. I also tried executing select queries that take around 15 seconds to run, and those completed normally. I want to make the application throw a database exception instead. How can I make this work?
I ran this test to eliminate the JDBC driver as a suspect:
java.util.Properties props = new java.util.Properties();
Class.forName("oracle.jdbc.driver.OracleDriver");
props.setProperty("user", "teng_oaam");
props.setProperty("password", "******");
java.sql.Connection conn = java.sql.DriverManager.getConnection("jdbc:oracle:thin:@******:1521:brsadb", props);
System.out.println(conn.getMetaData().getDriverName() + " " +conn.getMetaData().getDriverVersion());
java.sql.Statement stmt = conn.createStatement();
stmt.setQueryTimeout(1);
System.out.println(stmt.getClass());
System.out.println(new java.util.Date());
try {
// this query takes about 20 seconds to execute
java.sql.ResultSet rs = stmt.executeQuery("select * from vcrypt_ip_location_map where from_ip_addr<=1160157297 and to_ip_addr>=1160157297");
} catch (Exception ex) {
ex.printStackTrace();
System.out.println(new
java.util.Date());
The query fails with ORA-01013, which is what I expect to happen, so the problem is not in my JDBC driver.
Thanks,
Josh Davis

Answer 1

public static Integer executeUpdate(TopLinkDBMgr topLinkDBMgr, BharosaDBQuery dbQuery) throws BharosaDBException {
   DataModifyQuery query = null;
   List args = Collections.EMPTY_LIST;
   long startTime = System.currentTimeMillis();
   try {
      AbstractSession session = (AbstractSession) topLinkDBMgr.beginSession(); +// creates a ClientSession and calls session.beginTransaction()+
      query = new DataModifyQuery();
      query.setCall(new SQLCall(dbQuery.getQueryString().replace(':', '#'))); +// we still have some SQL queries we haven't changed since we used Hibernate+
      Vector arguments = bindArgumentsForRawSql(dbQuery, query);
      args = arguments;
      query.setQueryTimeout(1);
      Object result = session.executeQuery(query, arguments);
      return converter.toInteger(result);
   } catch (BharosaDBException ex) {
      throw ex;
   } catch (Exception e) {
      throw BharosaDBException.createDBObjectQueryException(dbQuery.getQueryString(), e);
   } finally {
      topLinkDBMgr.endSession(); +// calls session.endTransaction() on the ClientSession+
      long time = System.currentTimeMillis() - startTime;
      Level level = getLogLevelForElapsedTime(time);
      if (logger.isEnabledFor(level)) {
         String message = buildPerformanceMessage(query, args);
         logPerformance(level, time, message);
For my test, I lock a table in SQL*Plus, and there is a background process that uses this method to update that table. That process hangs until I release the lock in SQL*PLus.
This is a corner case, though. Most of our updates are done with the UnitOfWork class, so I need to be able to make the queries that it generates time out also.
Thanks,
Josh