[Red5devs] Too much inactivity - Calling disconnect callbacks?

[Steven Gong]

You can change pingInterval to 0 so that the keep-alive job will be
disabled.

On Sun, May 25, 2008 at 2:22 AM, Matt Hodgson <mhodgson at youcastr.com> wrote:

> Hey guys, I posted this on the user list and didn't get a response so
> I figured I'd try here.
>
> I'm seeing the occasional "too much inactivity" message in my logs
> (production) and it appears that when clients are disconnected with
> this method the call backs (such as roomDisconnect, appDisconnect,
> etc.) are not being triggered.
>
> Is this the desired behavior? I know in my case it causes my listener
> objects (in the web server db) to be left as "live" indefinitely since
> the synchronization methods in roomDisconnect are not called.
>
> Can you guys:
>
> 1. Verify that this is indeed the desired behavior
> 2. Provide me some quick direction on how I might be able to modify
> this? My gut says maybe to just call the close method (in
> RTMPCOnnection) in the KeepAliveJob method when the "too much
> inactivity" is triggered.
>
> Thanks for the help.
>
> -Matt
>
> _______________________________________________
> Red5devs mailing list
> Red5devs at osflash.org
> http://osflash.org/mailman/listinfo/red5devs_osflash.org
>



-- 
Best Regards
Steven Gong

InfraRed5 Red5 Consultant: http://www.infrared5.com, steven at infrared5.com

Red5 Developer: http://osflash.org/red5,
http://jira.red5.org/confluence/display/~steven/Home

Javaflash Project Founder and Maintainer: http://osflash.org/javaflash
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://osflash.org/pipermail/red5devs_osflash.org/attachments/20080525/e0ed414e/attachment.html