I just updated to Jetty 6.1.6rc1 and Dojo 1.0, and I'm hitting the same problem. I have Jetty hosted on one computer with Firefox connected to Cometd. I then have another computer on WiFi with Firefox, IE6, IE7, Safari, and Opera all connected to Cometd. After connecting, I first let it idle for a bit, then I hit refresh on all of the browsers. After idling for another while, all 5 browsers on the remote computer simultaneously lose connection. However, the Firefox browser that's running locally on the server has no problems. I recorded the whole session on the remote computer with Wireshark if you want the dump file.
Regarding the error handling, it would be good to have hooks for different events such as connected, reconnecting, disconnected, subscribed, error, etc.
What did you mean by "connect to the implementation"?
-Geoffrey Lee
;
On 11/5/07, Greg Wilkins <mortbay.com" target="_blank">gregw mortbay.com> wrote:
Geoffrey,
currently there is no standard way to report connection failures,
but you can connect to the implementation if you really need to now.
This is one of the key features that we need to add very soon.
As for what caused that actual error, I have not seen it
before. ;I would need to see a tcpdump to diagnose more.
What version(s) were you using? I recommend trying the
1.0rc of dojo against the 6.1.6rc1 release of Jetty.
Both have received considerable work in the last few weeks.
cheers
Geoffrey Lee wrote:
>; Hi guys,
> I'm using the Jetty implementation, and I'm occasionally getting an
> "Error: Bad httpd response code:0" in Firefox 2.0.0.6 <
http://2.0.0.6>.
> When this happens, the client will not attempt to reconnect, and there's
> no indication to the user that an error occurred unless you look at
> Firebug. Is there some way to setup an exception handler for this?
>
> Here's the POST:
> message=%5B%7B%22channel%22%3A%20%22%2Fmeta%2Fconnect%22%2C%20%22connectionType%22%3A%20%22long-polling
> %22%2C%20%22clientId%22%3A%20%221dvrvc6pjishq%22%2C%20%22timestamp%22%3A%20%22Sat%20Nov%2003%2016%3A45
>
> %3A32%20CDT%202007%22%2C%20%22id%22%3A%20%22uxpypr%22%7D%5D
>
> This is what Firebug says:
> Error: bad http response code:0 message= bad http response code:0
>; dojo.js (line 20)
> tunnel opening failed: Error: bad http response code:0 message=bad http
> response code:0 cometd.js.uncompr.. . (line 837)
> TypeError: dojo.cometd has no properties message= dojo.cometd has no
> properties
dojo.js (line 20)
>
>
> -Geoffrey Lee
>
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "cometd-dev"; group.
To post to this group, send email to cometd-devgooglegroups.com
To unsubscribe from this group, send email to cometd-dev-unsubscribegooglegroups.com
For more options, visit this group at http://groups.google.com/group/cometd-dev
Visit the cometd website at http://www.cometd.com/
-~----------~----~----~----~------~----~------~--~---
|
