This is a strange behavoiur,

i've written a videochat application, with some server side code.

I have an application.onDisconnect that catch the closing of the client...

With ONLY A COMPUTER where i'm testing the server don't catch the closing
of the client.

This client connects well, everything is initialised, but when is called
the nc.close() or when i just close the browser window no ondisconnect
event happens, leaving the video slot open!!!!

What are the possible causes of this? I repeat, this happens only with ONE
client, for other computers disconnection works well

Thanks in advance

Alfonso Florio


=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

[ Post a follow-up to this message ]

This is a known issue of FCS, also known as the
"GHOST" bug.

One solution I've seen is every clients sends a
message to the sever every 15 seconds. Every 30
seconds the server checks the messages. If one message
has not been updated the respective client is
disconnected.

But I know there are simpler ones too!

--- Alfonso Florio <a.florio-hPLUXwcWdVo@public.gmane.org> wrote:

> This is a strange behavoiur,
>=20
> i've written a videochat application, with some
> server side code.
>=20
> I have an application.onDisconnect that catch the
> closing of the client...
>=20
> With ONLY A COMPUTER where i'm testing the server
> don't catch the closing=20
> of the client.
>=20
> This client connects well, everything is
> initialised, but when is called=20
> the nc.close() or when i just close the browser
> window no ondisconnect=20
> event happens, leaving the video slot open!!!!
>=20
> What are the possible causes of this? I repeat, this
> happens only with ONE=20
> client, for other computers disconnection works well
>=20
> Thanks in advance
>=20
> Alfonso Florio
>=20
>=20
>
=3D-----------------------------------------------------------
> Supported by Fig Leaf Software -
> http://www.figleaf.com
>
=3D-----------------------------------------------------------
>=20
> To change your subscription options or search the
> archive:
>
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>=20



=09
__________________________________=20
Yahoo! Mail=20
Stay connected, organized, and protected. Take the tour:=20
http://tour.mail.yahoo.com/mailtour.html=20


=3D-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=3D-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

[ Post a follow-up to this message ]

Could be a firewall or proxy between that client and the server trapping
the socket and not letting it go. If flashcom is not notified that the
TCP socket is killed, it can't manifacture an onDisconnect out of the
blue! Give it a minute though, FCS has a built-in timeout. Or you can
"tickle" each client with a ping or a s2c call to make it happen faster.

Peldi=20

-----Original Message-----
From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
[mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.
org] On Behalf Of Alfonso
Florio
Sent: Thursday, July 28, 2005 8:09 AM
To: FlashComm Mailing List
Subject: [FlashComm] the application sometime don't disconnect!

This is a strange behavoiur,

i've written a videochat application, with some server side code.

I have an application.onDisconnect that catch the closing of the
client...

With ONLY A COMPUTER where i'm testing the server don't catch the
closing=20
of the client.

This client connects well, everything is initialised, but when is called

the nc.close() or when i just close the browser window no ondisconnect=20
event happens, leaving the video slot open!!!!

What are the possible causes of this? I repeat, this happens only with
ONE=20
client, for other computers disconnection works well

Thanks in advance

Alfonso Florio


=3D-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=3D-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

[ Post a follow-up to this message ]

On 7/28/05, Naicu Octavian <naicuoctavian-/E1597aS9LQAvxtiuMwx3w@public.gmane.org> wrote:[vb
col=seagreen]
> This is a known issue of FCS, also known as the
> "GHOST" bug.
>=20
> One solution I've seen is every clients sends a
> message to the sever every 15 seconds. Every 30
> seconds the server checks the messages. If one message
> has not been updated the respective client is
> disconnected.
>=20
> But I know there are simpler ones too!
>=20[/vbcol]

We've had the exact same issue, and solved it with a similar solution.
(The server sends a "hello?" message to the client every 30 seconds,
and the client responds with "I'm alive still!" and if the server
doesn't get a response after 2 attempts, it disconnects them.)

-David R

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

[ Post a follow-up to this message ]

Vi how does the client and server side code look like???

/Thomas Petersen
----- Original Message -----
From: "David Rorex" <drorex-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@pub
lic.gmane.org>
Sent: Thursday, July 28, 2005 10:22 PM
Subject: Re: [FlashComm] the application sometime don't disconnect!


On 7/28/05, Naicu Octavian <naicuoctavian-/E1597aS9LQAvxtiuMwx3w@public.gmane.org> wrote:[vb
col=seagreen]
> This is a known issue of FCS, also known as the
> "GHOST" bug.
>
> One solution I've seen is every clients sends a
> message to the sever every 15 seconds. Every 30
> seconds the server checks the messages. If one message
> has not been updated the respective client is
> disconnected.
>
> But I know there are simpler ones too!
>[/vbcol]

We've had the exact same issue, and solved it with a similar solution.
(The server sends a "hello?" message to the client every 30 seconds,
and the client responds with "I'm alive still!" and if the server
doesn't get a response after 2 attempts, it disconnects them.)

-David R

=---------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=---------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm


=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

[ Post a follow-up to this message ]

--- Peldi Guilizzoni <gguilizzoni-14osZcCZf762oZ/6fjIToQ@public.gmane.org>
wrote:

> Could be a firewall or proxy between that client and
> the server trapping
> the socket and not letting it go. If flashcom is not
> notified that the
> TCP socket is killed, it can't manifacture an
> onDisconnect out of the
> blue! Give it a minute though, FCS has a built-in
> timeout. Or you can
> "tickle" each client with a ping or a s2c call to
> make it happen faster.
>=20
I would no rely on the FCS timeout, I've seen
connections being up for days since the man who opened
it left the chat room!




> Peldi=20
>=20
> -----Original Message-----
> From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gman
e.org] On
> Behalf Of Alfonso
> Florio
> Sent: Thursday, July 28, 2005 8:09 AM
> To: FlashComm Mailing List
> Subject: [FlashComm] the application sometime don't
> disconnect!
>=20
> This is a strange behavoiur,
>=20
> i've written a videochat application, with some
> server side code.
>=20
> I have an application.onDisconnect that catch the
> closing of the
> client...
>=20
> With ONLY A COMPUTER where i'm testing the server
> don't catch the
> closing=20
> of the client.
>=20
> This client connects well, everything is
> initialised, but when is called
>=20
> the nc.close() or when i just close the browser
> window no ondisconnect=20
> event happens, leaving the video slot open!!!!
>=20
> What are the possible causes of this? I repeat, this
> happens only with
> ONE=20
> client, for other computers disconnection works well
>=20
> Thanks in advance
>=20
> Alfonso Florio
>=20
>=20
>
=3D-----------------------------------------------------------
> Supported by Fig Leaf Software -
> http://www.figleaf.com
>
=3D-----------------------------------------------------------
>=20
> To change your subscription options or search the
> archive:
>
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>=20
>
=3D-----------------------------------------------------------
> Supported by Fig Leaf Software -
> http://www.figleaf.com
>
=3D-----------------------------------------------------------
>=20
> To change your subscription options or search the
> archive:
>
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>=20


 ________________________________________
__________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around=20
http://mail.yahoo.com=20

=3D-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=3D-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

[ Post a follow-up to this message ]

I came across this bug quite some time ago, and Peldi's suggestion to
'tickle' connected clients with a ping at a set interval works really wel=
l.

I agree that waiting for a timeout is not a very good idea, as it is high=
ly
unreliable. In my experience, FCS fails to ever notice that a client is g=
one
when an onDisconnect() is bypassed.

I have also found that when the onDisconnect function is missed, and an
application is forcefully disconnected (say, at the event of no ping repl=
y),
FCSs data for that client is corrupted. Stream name and application name =
is
sometimes dropped, and the bytes_out value is always incorrect (in the or=
der
of ~2GB/~4GB/~8GB - even if the client was only connected for a few
seconds).

I am still really keen to get to the bottom of this, so if anyone else ha=
ve
experienced such erroneous data, please let me know, as I would like to k=
now
in which context this happens. My findings indicate that it is only in th=
e
event of a missed onDisconnect().

Thanks,
Simon Skr=F8dal


----- Original Message -----
From: "Naicu Octavian" <naicuoctavian-/E1597aS9LQAvxtiuMwx3w@public.gmane.or
g>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@pub
lic.gmane.org>
Sent: Friday, July 29, 2005 5:59 AM
Subject: RE: [FlashComm] the application sometime don't disconnect!


>
> --- Peldi Guilizzoni <gguilizzoni-14osZcCZf762oZ/6fjIToQ@public.gmane.org>
> wrote:
> 
>  I would no rely on the FCS timeout, I've seen
> connections being up for days since the man who opened
> it left the chat room!
>
>
>
> 
> =3D----------------------------------------------------------- 
> =3D----------------------------------------------------------- 
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm 
> =3D----------------------------------------------------------- 
> =3D----------------------------------------------------------- 
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm 
>
>
>  ________________________________________
__________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> =3D-----------------------------------------------------------
> Supported by Fig Leaf Software - http://www.figleaf.com
> =3D-----------------------------------------------------------
>
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>


=3D-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=3D-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

[ Post a follow-up to this message ]

you are right... the "ghost" connections remain active for hours!!!

also pinging is not a solution

i have to use a remote method


At 22.29 28/07/2005, you wrote:

>--- Peldi Guilizzoni <gguilizzoni-14osZcCZf762oZ/6fjIToQ@public.gmane.org>
>wrote:
> 
>  I would no rely on the FCS timeout, I've seen
>connections being up for days since the man who opened
>it left the chat room!
>
>
>
> 
>=----------------------------------------------------------- 
>=----------------------------------------------------------- 
>http://chattyfig.figleaf.com/mailman/listinfo/flashcomm 
>=----------------------------------------------------------- 
>=----------------------------------------------------------- 
>http://chattyfig.figleaf.com/mailman/listinfo/flashcomm 
>
>
> ________________________________________
__________
>Do You Yahoo!?
>Tired of spam?  Yahoo! Mail has the best spam protection around
>http://mail.yahoo.com
>
>=-----------------------------------------------------------
>Supported by Fig Leaf Software - http://www.figleaf.com
>=-----------------------------------------------------------
>
>To change your subscription options or search the archive:
>http://chattyfig.figleaf.com/mailman/listinfo/flashcomm


=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

[ Post a follow-up to this message ]