Re: Error: Bad http response code:0

Geoffrey Lee wrote:
> I played around with it a bit more, and I'm pretty
convinced that it's
> the WiFi connection being slightly unreliable because
I'm not
> experiencing this on a wired connection. I think all we
need to do is
> add some way to reconnect for dropped connections. I'm
going to dive
> into the cometd client code tonight and see what I can
come up with.

Geoffrey,

I can get that error by stopping and restarting the server.

But there is a bug, as the client should receive reconnect
advice that
says do another handshake.  So the client should recover.

I will also investigate later today.

cheers


> -Geoffrey Lee
> 
>  
> On 11/6/07, *Greg Wilkins* <gregwmortbay.com
> <mailto:gregwmortbay.com>> wrote:
> 
> 
>     Geoffrey Lee wrote:
>     > 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
> 
> 
>     Geoffrey,
> 
>     I'll try to reproduce following your description.
> 
>     If I can't then I'll ask for the dump file.
> 
>     cheers
> 
> 
> 
> 
>     > 


--~--~---------~--~----~------------~-------~--~----~
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://grou
ps.google.com/group/cometd-dev

Visit the cometd website at http://www.cometd.com/
-~----------~----~----~----~------~----~------~--~---

Ah,

I just realized what it is.

There is no reconnect advice as the connect fails when the
connection to the
server is lost.

I need to implement the backoff connect mechanism that was
discussed at the
face 2 face.

I'll see what I can do over the next few days.

cheers


--~--~---------~--~----~------------~-------~--~----~
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://grou
ps.google.com/group/cometd-dev

Visit the cometd website at http://www.cometd.com/
-~----------~----~----~----~------~----~------~--~---