Fill never completes over RTMP ..

[vitopn]

I am having an odd issue that seems to be specific to the
RTMP (or RTMPS) channel.



Certain fills do complete when they are run on an RTMP
channel. if I switch the channel to HTTP everything works well. One
other thing I noticed is that when the client and server where on
the same machine the fill completed even when using RTMP, the
problem only seems to occur when the client and server are on
different machines.



Some other observations:

I have had this happen in two separate projects. One using
RTMPS and another using RTMP.

I've tried turning the FDS server logs to DEBUG and it
appears that the fill completes OK (I see the serialization of the
list).



Has anyone seen this? Any thoughts?

[Former Community Member]

If you haven't already done so, I would recommend that you
upgrade to LCDS 2.5, which has many RTMP and RTMPS fixes.





HTH

Kumaran

[vitopn]

OK.



When I upgrade I get the following error when I run the
client (VerifyError: Error #1053: Illegal override of subtopic in
mx.messaging.Consumer.).



I couldn't find any instructions for upgrading from FDS to
LCDS 2.5 ... am I missing something?

[Former Community Member]

Note that you must update to Flex Builder 2.0.1 Hotfix 2
along with LCDS

2.5. Be sure that your Flex project Library Path is pointing
to the updated

swcs from Flex SDK 2.0.1 Hotfix 2 and ensure that fds.swc and
fds_rb.swc

are the updated ones from LCDS 2.5.

[vitopn]

OK I was able to upgrade. From my small project the upgrade
resolved the problem and all is well. For my larger project the
problem seemed to get worse there were several fills that just
never completed (the server sends the response but the client
doesn't seems to get it).



Are we the only one seeing this?

[vitopn]

Someone posted with the same issue on the yahoo group
FlexCoder's group (
http://tech.groups.yahoo.com/group/flexcoders/message/79986)
so I know I'm not the only one having this issue. Anyone have any
thoughts?



I've tried HotFix 3 .. I'm rolling back (again) to FDS ..
until we have time to port to another more stable messaging
solution.