Hi, Chandan,
Grizzly, by default, has limited number of HTTP requests it may
process on single connection (to avoid some kind of DoS attacks).
So, probably, you observe such a behavior because of that mechanism.
You can disable it by setting:
selectorThread.getMaxKeepAliveRequests(-1);
I could be wrong, but let's try that solution and then will see if it
helps or not.
WBR,
Alexey.
On Jul 15, 2009, at 8:10 , chandan_evol wrote:
>
> Hi All,
> I am using Grizzly 1.9.15 as a HTTP web server for my
> application.
> But, whenever the client side sends number of requests (~10 requests
> in
> second), the application sends RST packets to the client, after
> sending FIN
> to the client side. This seems that the Grizzly server is dropping
> some
> requests if it is heavily loaded. Can someone tell me what can
> prevent the
> Grizzly server to drop requests. The client is maintaining an HTTP
> non-persistent connection where everytime connection will be closed
> if there
> is a response received for a request.
> I would appreciate if someone gives me a solution.
>
> thanks in advance
>
> Chandan
> --
> View this message in context: http://www.nabble.com/RST-FIN-sent-from-the-Grizzly-server-tp24492450p24492450.html
> Sent from the Grizzly - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>