Le mardi 24 juillet 2007 à 10:08 -0700, Niels Joubert a écrit : > This error occurs when the client timeouts. I get it when Red5 is > spinning through large files to create the index and the client is left > hanging. Red5 the automatically timeouts after a while. im not sure on > that appDisconnect one...
Thanks for the reply Niels, is anyone know if the appDisconnect() function is call when a user connection is on timeout ? > > Guillaume Lecanu wrote: > > Hi, > > > > Sometimes we can see in our logs : > > > > [WARN] 324931796 DefaultQuartzScheduler_Worker-1:( > > RTMPConnection.execute ) Closing RTMPMinaConnection from 10.0.0.2:1772 > > to dev.box:80 (in: 1175450, out: 3638) due to too much inactivity > > (1185251054945). > > > > > > In which cases this could happen ? I supposes it's only if a connected > > users doesn't uses any services of Red5 since the specified timeout time. > > > > When this error occur, is the appDisconnect() function is called ? > > > > Thanks a lots ! > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Red5 mailing list > > [email protected] > > http://osflash.org/mailman/listinfo/red5_osflash.org > > > > > _______________________________________________ > Red5 mailing list > [email protected] > http://osflash.org/mailman/listinfo/red5_osflash.org >
_______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
