hi guys,

I'm working on a new project.

I'm trying to find out about connection timeout exception. I've set the timeout of the connection to a limit, but weblogic does not accept it. It still referred to its xml file for its timeout period. I'm trying to resolve this by testing all possibities of getting/setting a timeout period.

At my side, I tried getting my program to connect to a non-existent website, and get "unknown host" error, whcih is logical. Is there any way I can test the SocketTimeoutException error?

umm... i think my topics are pretty messy...
Who is Participating?
girionisConnect With a Mentor Commented:
Yes it's a bug in the implementation of setTimeout. It means that the time taken for the timout to occur is double. I.e. if you set the timeout to 1000, it will take 2000 before it times out. Well, if it is so, then the only thing you have to do is to set half the time out of the required amount.
How are you setting socket timeout in URLConnection?
java_kevinAuthor Commented:
URL url = new URL(targetURL);
connection = (HttpURLConnection)url.openConnection();
try {

catch (SocketTimeoutException e) {


HttpURLConnection is a method that implements the abstract method from java's
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

What version of WebLogic are you using? If >= Weblogic 9.0 then use setReadTimeout(int)
Ok you are using 8.1, still, try to use setReadTimeout(int)
java_kevinAuthor Commented:
umm, gosh, There is a difference between WebLogic 8.1 SP2 and SP6!

SP6 seems to provide setReadTimeout, while SP2 is still using setTimeout.

And accordingly to, setTimeout feature in SP2 seems buggy.

For SP2,, nothign was mentioned.

Any idea where I can get API documentation for weblogic 8.1 SP2? ;)
Can you upgrade to sp6?
java_kevinAuthor Commented:
No plans to do so at the moment.

But is this a bug? I mean, I can't really grasp the exact meaning it's trying to pass.

Does it mean, the calling of the method will be delayed, or it really refers to the value accepted by the method will be doubled?
java_kevinAuthor Commented:
oh.. that's... why..

alright, i'm asking the BEA side for an official confirmation of this issue, before I proceed to change the code again.

Will check back here again!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.