On Thu, May 14, 2009 at 10:49 PM, Igor Minar <iiminar_at_gmail.com> wrote:
>
> I'm surprised to hear that grizzly-sendfile is conflicting with comet and
> causing the double responses. I can't think of anything within
> grizzly-sendfile that would be causing this.
I am sure you are correct, I can use either of the filters
individually but not both at the same time. We'd very much like to
use both but the sample webapp I sent to JFA definitely fails with the
response doubling if both are in fact enabled.
> grizzly's api suggests that you can add multiple filters and all of them
> will be invoked at the right time, so if this causes problems then my
> feeling is that it is a grizzly bug.
I'd tend to agree, just waiting for JFA to reproduce and give some
guidance or feedback.
> The second issue when grizzly-sendfile caused comet to be disable even
> thought it was enabled via the domain.xml file is again something that could
> be improved in grizzly. Instead of
> -Dcom.sun.enterprise.web.connector.grizzly.asyncFilters=, there could be an
> option like -Dcom.sun.enterprise.web.connector.grizzly.appendAsyncFilter=,
> which would cause the specified filter to be appended to the filter chain
> rather than result in replacement of the existing chain with the new
> definition.
JFA provided a clean way, that worked, to enable both fitlers. This
particular issue is long resolved as far as I am concerned.
> If you have a simple app that manifests the double response problem then
> post it somewhere and I'll have a look at it over the weekend - no promises
> that I'll be able to fix it if the problem is a nontrivial grizzly bug
> though.
I'll send a link to the sample sources privately.
Thomas