if you whip up a simple war file, and let us have that with your
server.xml, then we can reproduce it and figure it out
Filip
On 09/16/2009 08:33 PM, Hacking Bear wrote:
But it seems not relate to my problem here, as I tried both ways. I also try
to close the response writer in addition to clo
But it seems not relate to my problem here, as I tried both ways. I also try
to close the response writer in addition to closing the event. Is that
necessary?
Another question is that why the TIMEOUT error keeps coming every few
seconds? Is it something intrinsic with the XMLHttpObject or ActiveXOb
On 09/13/2009 06:51 PM, Hacking Bear wrote:
On ERROR with subtype other than DISCONNECT, I just ignore it, i.e. no call
to event.close() nor trying to close the streams.
an error means you should always close, or you can leave a thread
spinning call error over and over again, you can't hold on
On ERROR with subtype other than DISCONNECT, I just ignore it, i.e. no call
to event.close() nor trying to close the streams. I also tried to do both on
any error but it seems not doing better. Besides, I didn't see any ERROR
other than TIMEOUT which repeats every few seconds.
Another note is that
Whis is the event.close conditional when there is an error, what if you
get a Comet report that says
Type=CometEvent.EventType.ERROR
Subtype=null
?
Filip
On 09/13/2009 01:25 PM, Hacking Bear wrote:
} else if (event.getEventType() == CometEvent.EventType.ERROR) {
final EventSubTy
Hi,
I have been battling with the comet event handling for a few weeks. The main
symptom is that the CPU usages may go high (60%), especially from a Firefox
connection. My page flow looks like:
- start firefox
- go to a login page to start a http session
- go to a page with comet subscription, see
