Hi Franklin,
looks like keep alive timeout works only for server accepted
connections, not client ones.
Can you pls. show your code how you establish client connections, may
be I'll be able to help you.
Thanks.
WBR,
Alexey.
On Oct 15, 2010, at 21:53 , Franklin Franca wrote:
>
> Hi.
>
> I am using Sailfin. I wrote one application that RECEIVES a request
> from
> SIPP, process the request and send the response (200 OK). I changed
> the
> domain.xml KeepAliveTimeoutInSeconds parameter from -1 to 60. So, I
> can see
> that after the application receives a request from SIPP if the
> application
> does not receive any request in 60seconds the connection is Closed
> (I am
> using TCP). EVERYTHING IS OK!
>
> I wrote another application that sends a REQUEST from Sailfin to
> SIPP. After
> the first request, one connection is stablished. After some
> inactivity time
> (for example 30 minutes) (in 30 minutes I have only one request)
> Sailfin is
> not closing the connection. IŽd like to close the connection. I
> changed in
> the GrizzlyNetworkManager.java in Sailfin source code the
> KeepAliveTimeoutInSeconds parameter from -1 to 60s but the
> connection is
> stablished forever.
>
> Could you please help me and tell me what is wrong?
>
> Thanks.
>
> Franklin.
>
> --
> View this message in context: http://old.nabble.com/Grizzly-Sailfin-Timeout-tp29974771p29974771.html
> Sent from the Grizzly - Development mailing list archive at
> Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>