Hi Dipankaj,
that's interesting requirement.
We never limit the number of active connections, though by configuring
thread pool - you can set the max number of active requests being
processed simultaneously.
Will it work for you?
Thanks.
WBR,
Alexey.
On Nov 10, 2010, at 7:23 , dipankaj wrote:
>
> Hi
> I am using GrizzlyWebServer as embeded WS in my application. But as
> per
> requirment, i need to configuration the number of active connections
> at a
> time the server should handle.
>
> Can you please let me know how i should proceed for the same.
>
> My sample code is
>
> GrizzlyWebServer gws = new GrizzlyWebServer(8080);
>
> ServletAdapter jerseyServletAdapter = new ServletAdapter();
> jerseyServletAdapter.setServletInstance(new ServletContainer());
> jerseyServletAdapter
> .addInitParameter
> ("com.sun.jersey.config.property.packages","my.test");
> jerseyServletAdapter.setServletPath("/");
>
> jerseyServletAdapter.addFilter(new MyFilter(), "MyFilterName", null);
>
> gws.addGrizzlyAdapter(jerseyServletAdapter, new String[] {"/"});
>
> gws.start();
>
>
> Thank you in advance
>
> Regards
>
> Dipankaj
> --
> View this message in context: http://old.nabble.com/configuration-of-the-number-of-active-connections-for-GrizzlyWebServer-tp30177950p30177950.html
> Sent from the Grizzly - Development mailing list archive at
> Nabble.com.
>