| Register
Thursday, August 07, 2008   

Macromedia Updates Flash Comm Server

Created By  David Emberton, at  5/6/2004 - 2 comments.

Click to view this author's website.

Available for Windows and Linux, the new http://www.macromedia.com/support/flashcom/downloads_updaters.html will bump your version of FCS to 1.5.2. Here's a list of issues addressed:

- When receive audio/video is set to true message queue is not being cleared causing delay in message delivery.
- Calling send() method on proxy shared objects causing "Bad network data" error.
- Client ping returns true if client is in terminated state.
- Maximum latency allowed for live audio before the server starts dropping audio msgs is now configurable via a config key in Application.xml
- Tunneling failing on legacy proxy servers using HTTP 1.0 protocol.
- Server-side streams can cause application instance to abort if a message is sent over a closed stream.
- Server-side call to application.getStats() not taking into account tunneling overhead.
- JS string objects being prematurely garbage collected when system is under load.
- Memory leak if a remote method is invoked with more than 10 args.
- Script engine can cause CPU to peg at 100% and never recover.
- Potential deadlock in Flash Communication Admin Server if connection to admin server is aborted before admin server completes connection to FCS server.
- Server never release FLV files after usage. Server should only lock FLV files while accessing the files, this allows easy replacement, substitution, or removal of files when they are not in use.
- Memory leak when setting fps (Frames per second) with NetStream.receiveVideo().
- Admin APIs: getUserStats returns wrong values for stream ID's
- Admin APIs: getLicenseInfo returns Max_adaptors and Max_vhosts in decimal, should be rounded to integers
- Duplicate messages are being sent occasionally when playing back FLV/MP3 files. The duplicated messages will cause jitters in audio and is more often to happen when streaming through slow connections.
- JS setInteval not working; timer suddenly stops.
- Passing a responder object to a remoting call doesn't work.
- JS Stream.send() always send data with the last message time in the stream, but fails to adjust the timestamp of data messages when multiple send() are called apart in time. Server should maintain a clock time and adjust the time difference to the message time.
- Data and status messages should be caught in the script when valid handlers are setup for the JS Stream object.
- When streaming, latency for dropping audio messages changes from 8 seconds to 4 seconds.
- For live streaming, server now combines audio samples. This significantly reduces CPU usage when there are lot of subscribers.
- IDX files are no longer used by the server for playing/seeking. That means server will only create FLV files when recording and no IDX files will be created.
- Fixed race condition bug in streaming when multiple play, pause, and seek commands are sent by the player. A bug is found in the server that a NetStream.pause(false) after a NetStream.play() sometimes cause the stream to freeze. Pause(false) should have no effect on the NetStream if it is already playing.
- Mime-type for http request is now configurable via a conifg key in Application.xml.
- Component-wise addListener doesn't work
- Support recording in FLV 1.1 format.
- Fixed slow response problem when calling server-side Stream.length() on corrupted mp3 files.
- Fixed bug in stream publishing. In a case when a client is publishing to a stream and server takes over the stream through server side Stream.play(), client is not unpublished and continues to send data.
- Server crash in Linux when attempts to load an application where application has syntax error in the server side script
- If an attempt is made to get a stream's publisher stats at the same time the stream is unpublished, it could result in a null ptr exception.
- Premature gc of stream can cause crash when calling Stream.get() from server-side script.
- Fixed bug in server streaming: On append, messages sent to stream have same time stamp as last message recorded no matter when recorded.
- Fixed memory probelm - message pool not being gc'd
- Fixed memory problem - dns lookup cache not being gc'd

Thanks to all the engineers who no doubt poured out the sweat for this release. If you've installed the updater, leave a comment to let us know how it went.

Need Professional Help For Your ActionScript Project?
ActionScript.com Consulting Services provide top quality professional ActionScript consulting to businesses around the globe. If you have a professional project in need to world-class talent, tell us about your project by requesting a quote today.

Reader Comments

  1. anafis95  Replied:
    ( 4/8/2005 At 5:13 AM)

    hehehejirhashf safgsajkf

  2. anafis95  Replied:
    ( 4/8/2005 At 5:17 AM)

    gag ag

Login to post your comments. If you do not have an account with us please Register.
Copyright 2005 by ActionScript, Inc.   |  Privacy Statement  |  Terms Of Use  |  ActionScript Client Extranet