DWR needs to be configured with a special load monitor when we are using a fancy container. e.g. from ContainerUtil:
if (servletConfig.getServletContext().getServerInfo().startsWith("jetty-6"))
{
container.addParameter(ServerLoadMonitor.class.getName(), ThreadDroppingServerLoadMonitor.class.getName());
}
else
{
container.addParameter(ServerLoadMonitor.class.getName
(), DefaultServerLoadMonitor.class.getName());
}
What's the best way of detecting Grizzy?
Thanks,
Joe.
On Nov 22, 2007 5:30 PM, Jeanfrancois Arcand <
Jeanfrancois.Arcand@...> wrote:
Joe Walker wrote:
>
>
> On Nov 22, 2007 3:37 AM, Jeanfrancois Arcand
Hum looks like the repo in not in sync (hopefully that's because
Thanksgiving in the US)...I've temporary placed the jar here:
http://weblogs.java.net/blog/jfarcand/archive/continuation-1.6-SNAPSHOT.jar
Hopefully that one doesn't gives 404 :-).
BTW I forgot to said I've tested with the examples that comes with the
dwr.war
. Also, to try in glassfish you need to do:
% install glassfish
% vi ${glassfish.home}/domains/domain1/config/domain.xml
% Search for:
<property name="proxiedProtocols" ...>
replace it with
<property name="cometSupport" value="true"/>
Restart and deploy :-)
Thanks!
-- Jeanfrancois
>
>
> I got a 404 for this. Did I look too early?
>
> Joe.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail:
dev-unsubscribe@...For additional commands, e-mail:
dev-help@...