Any chance you are using RTMPS, not RTMP? There is a bug in RTMPS for the 2.6 release:
Description: LCDS-358: RTMPS writes by LCDS may stall when network TCP buffers back up We've got a hotfix that addresses that problem... feel free to contact me off list ([EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]> if that is what you are running into). If not, if you could the next best step would be to turn on the "*" debug pattern to see if we can catch an instance of that hang occurring in the debug logs. Feel free to send them to me as well and we'll take a look to see if we can spot the hang. Jeff From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of jardillier Sent: Tuesday, September 16, 2008 1:03 AM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: LCDS data serialization frozen Hello, I am using the LCDS 2.6 and the channel RTMP. About the stack dump of the JVM i think that this should be displayed in the server.log file, and nothing were writen indicating a deadlock. --- In flexcoders@yahoogroups.com<mailto:flexcoders%40yahoogroups.com>, Jeff Vroom <[EMAIL PROTECTED]> wrote: > > What version of LC DS are you using and what type of channel (i.e. is it an RTMP or RTMPS channel or one of the app server's http based channels)? > > Another thought is to get a stack dump from your JVM when this happens to be sure there is not a deadlock or something like that. > > Jeff > > From: flexcoders@yahoogroups.com<mailto:flexcoders%40yahoogroups.com> [mailto:flexcoders@yahoogroups.com<mailto:flexcoders%40yahoogroups.com>] On Behalf Of jardillier > Sent: Monday, September 15, 2008 1:47 AM > To: flexcoders@yahoogroups.com<mailto:flexcoders%40yahoogroups.com> > Subject: [flexcoders] LCDS data serialization frozen > > > Hi all, > i have a strange behaviour of the serialization, it seems to be > frozen. This is a problem that occurs randomly. Sometimes, when i > start my application i didn't recieved the data from the server to the > client. When i had a look to the server.log file i saw that the > serialization ran, i mean there is the log MYDESTINATION.fill ([ all > my objects ...]) and then nothing more. What i try to explain is that > normally i saw in this log these objects (as mentionned previously) > and just after there is lines like "caching > Item:MYDESTINATION{ID=123456}(1234567)" and these lines do not exist. > This is why i think that the serialization is frozen (probably not the > good word but it expresses the behaviour). > Any ideas ? > Many thanks per advance >
<<inline: image001.jpg>>
<<inline: image002.jpg>>
