Hi,
Well I cannot comment on Solaris. But Grizzly performs dramatically
different on Windows as opposed to Linux, due to differences as to how
the JVM NIO implementation on that platform works. Currently on Linux
due to and underlying JVM bug, it simply doesn't work and it regularly
runs into CPU spikes which means that the application is unavailable to
handle more connections with the system responding with RST packets.
Hopefully there are some Grizzly users with Solaris knowledge that can
clarify how well it works.
Rgds,
James
On Tue, 2009-07-14 at 23:19 -0700, chandan_evol wrote:
> Hi All, I am using solaries 10 as the platform. thanks chandan
> 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: Re: RST/FIN sent from the Grizzly server
> Sent from the Grizzly - Users mailing list archive at Nabble.com.