ok -- i will use your servlet -- didnt notice before -- but still have it.
but -- to be clear -- i determined i had the issue initially without using a proxy --
it was directly from web browser at friends home computer to my computer.
and it was 30seconds.
did you change the timeout -- or are your saying no issue at 120 seconds with default
configuration ?
and that is why i added the question :
---------
BUT -- what about the more general question of WHY it works this way ???
why timeout connections that are moving data ? is there not a way to know the connection is in use
moving data and not just "idle".???
--------
thanks
gary
----- Original Message -----
From: Oleksiy Stashok
To: users_at_grizzly.dev.java.net
Sent: Thursday, March 04, 2010 1:10 PM
Subject: Re: 30second timeout
Hi,
On Mar 4, 2010, at 21:14 , emiddio-verizon wrote:
i will take your word for it for the moment;
i have not been able to go to another site to test my gvf3 dnload/upload after changing the timeout parameters;
i cannot connect to my server from home -- from the internet side of the dsl modem unless i use a web-proxy -- which
could have its own timeout issues.
maybe i can put together something to let me talk to my server but deliberately slow the connection down.
Ok.
BUT -- what about the more general question of WHY it works this way ???
why timeout connections that are moving data ? is there not a way to know the connection is in use
moving data and not just "idle".???
Well, as I told I think it's web proxy closes connections by timeout. You can run the servlet I sent you in last email on localhost and make sure it's not grizzly/glassfish, who breaks the connection.
WBR,
Alexey.