thanks.
My issue is not from the server side but from my application.
My application is like IE, it connects to a http server.
What JDK version are you using?
on 1.5+ you can set the timeout yourself.. There is *NO* default timeout
set on HTTPUrlConnection hence it'll block indefinitely. On 1.4, you can
set some system properties to set a global timeout on all sockets, but
that's most likely not a good thing.
If you are stuck using older JDK's, then look at using apache's commons-http
instead.
> thanks.
> My issue is not from the server side but from my application.
[quoted text clipped - 43 lines]
>> .......
>> </web-app>
Lew - 04 Apr 2007 23:48 GMT
> [top=posted message in response to:]
"clir" <christophe.leroquais@gmail.com> wrote in another top-posted message ...
A: Because it makes posts harder to read.
Q: Why is it bad?
A: Posting the reply to a message above the quoted text instead of in line.
Q: What is top-posting?

Signature
Lew
Arne Vajhøj - 05 Apr 2007 01:53 GMT
> What JDK version are you using?
>
[quoted text clipped - 5 lines]
> If you are stuck using older JDK's, then look at using apache's commons-http
> instead.
In a client app it may be OK.
And to save the original poster the trouble of finding it:
System.setProperty( "sun.net.client.defaultConnectTimeout", "100");
Arne