Forum Stats

  • 3,827,608 Users
  • 2,260,798 Discussions
  • 7,897,314 Comments

Discussions

setQueryTimeout() stopped working after upgrade from 10g to 11g

mpapesch
mpapesch Member Posts: 12
Hi,

we are upgrading our database server from Oracle 10g to 11g and are experiencing a strange problem: the JDBC statement <tt>cancel()</tt> and <tt>setQueryTimeout()</tt> methods no longer work.

Starting out with the information given in [1,2], what we found out so far is that there seems to be a combination of a different behavior of the database and some kind of network issue.

While 10g accepted the <tt>cancel()</tt> request and promptly answered with the corresponding <tt>ORA-01013</tt> (user requested cancel of current operation), 11g seems to try and contact the client for a confirmation of the cancellation.

If the client is in the same subnet as the database server everything works as expected.

If, however, the client is in a different subnet, this request from the database server does not make it back to the client through the firewall.

Right now we are kind of stuck and any help, reference to documentation, workarounds and questions are greatly appreciated.

I'll be glad to gather and provide further information.


Thanks in advance,

Matthias


[1] http://stackoverflow.com/questions/2376615/how-is-oracles-jdbc-query-timeout-implemented
[2] http://blog.tanelpoder.com/2010/02/17/how-to-cancel-a-query-running-in-another-session/
Tagged:

Answers

This discussion has been closed.