URLConnection timeout in JDK 1.0.2

I am calling URL's from my applet with some specified parameters, this URL then performs a query against a database.  These queries can take anywhere from seconds to an hour.  With the longer queries, java receives an IOException after about 10 minutes of waiting.  Is there any way around this behavior?

Also, when I try to recover from this IOException, the next call to the web server isn't accepted.  Is this because these two requests are in the same thread and it thinks the other connection is still open?  The other connection shouldn't still be open though, as I call my closing method in the finally block after I catch the first IOException.

Any help would be appreciated.  Thanks.
lmarlowAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jhanceCommented:
I don't believe that you can change this behavior.  At least not in your Java application.  I think you are running into an underlying operating system timeout that is eventually getting back to Java as an error.  How about another suggestion?  Instead of just having the connection sit idle while your query processes, how about sending back a progress update every so often?  Not only would this keep the time-out from happening, it might pacify your savage user who doesn't know why the darned thing is taking so long.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
lmarlowAuthor Commented:
So, if I was to send back some sort of progress indicator, the OS would think that the connection was still alive, and keep it open?  Or does would it close it after 10 minutes anyway, just because it doesn't like to have HTTP requests open for more than 10 minutes?

Do you have any idea why the web server wouldn't accept another request while the initial page was being processed?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Java

From novice to tech pro — start learning today.