Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8029749
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 5, 20262026-06-05T00:31:50+00:00 2026-06-05T00:31:50+00:00

I have a query that runs longer than the value specified with oracle.jdbc.ReadTimeout. It

  • 0

I have a query that runs longer than the value specified with oracle.jdbc.ReadTimeout. It fails with an SQLRecoverableException which is all good. Except the query doesn’t can cancelled and the Oracle keeps working on it. Trying to catch that exception and do a cancel on the statement fails because the statement is already closed.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-05T00:31:52+00:00Added an answer on June 5, 2026 at 12:31 am

    This was silly. The query timeout should be set with Statement.setQueryTimeout() and then queries will be cancelled properly. Basically setQueryTimeout should always be lower than the oracle.jdbc.ReadTimeout and everyone will be happy.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have the following query that runs in my Oracle database and I want
I have this query that runs fine: SELECT Value FROM data WHERE MetaDataID =
I have the following query that runs as part of a CRON job, which
I have a powershell process that runs on demand which collects all Request History
I have a quite complex multi-join TSQL SELECT query that runs for about 8
For example I have a mysql query that gets some data. Then runs another
I have a Delphi 2009 application that runs a query over a database using
I have a php script that runs a mysql query, then loops the result,
I have a query that runs in about 2-4 minutes on production but runs
I have a fairly simple query that runs super fast most of the time

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.