Hi Zaid,
Thank you for taking to the time to reply to my request.
I think I may have confused everyone with my problems with Comet. I
actually have 2 outstanding problems that may or may not be related. One is
the problem with firewalls and AV and the other is the problem with dropouts
after an hour or so of idle time.
The problem with dropouts (or "Comet data into the bit bucket") is less
concerning to me than the other and I have put further investigation of it
in abeyance for now as I rewrite the servlets concerned for other reasons.
The problem with AV/firewalls is my top priority.
Further comments inline.
> thanks for the encouragement :-)
[JCT] You deserve it!
> The Dynamic Mashup Server embeds Grizzly with Grizzlets so I have a
> bit better control over the environment than just using the GlassFish
> install or Grizzly with Jetty, etc. I did experience the "Comet data
> into the bit bucket" issue when I was using various threads to start
> embedded Grizzly. Since I think you are using Servlets, are you sure
> that you are abiding with the threading rules for Servlet containers?
[JCT] Yes, I believe I am doing things correctly thread-wise but I will have
another look at things to be sure. Thanks for the tip.
> If I remember the Servlet spec, you can spawn threads at your leisure
> but can only post to the Response output stream from its thread and
> not yours. Perhaps your thread is getting GCed?
[JCT] You may be onto something here. But why would the thread get GCed if
it's still alive?
> The other possible issue which also may be categorized as the "Comet
> data into the bit bucket" issue is that the browser might be
> internally stopping the connection without warning. I think that this
> happens when you send more than 8 MB of data over the life of the
> Comet connection-- depending on the type of Comet connection.
[JCT] I don't think this is the reason as the dropouts are occurring even
when almost no data has been transmitted. It definitely seems to be only
related to time.
> So which browser are you using on Vista? and what's the Comet type?
> JavaScript code?
[JCT] For browsers, I have tried both IE 7 and Firefox 2.
The actual Comet type is interesting. We are completely unsure what to set
as the content type in the servlet response because what we are transmitting
is actually serialized Java objects. Which content type would correspond
with that?
You may well have helped diagnose the dropouts problem and the AV/firewall
issue may be related to the content type not being set correctly leading to
the AV software thinking that the data may be a virus or other threat.
I will keep you posted on what I discover in the course of further
investigation and thanks for your input.
Cheers,
John