Accessibility

Flash Communication Server Release Notes

Macromedia Flash Communication Server MX 1.5 Updater Release 2

This document applies to the Flash Communication Server MX 1.5 Updater Release 2. This Updater release works with Flash Communication Server MX 1.5 or 1.5.1 (FCS 1.5 Updater Release 1). This is a cumulative patch that includes all fixes in FCS 1.5.1. You may apply this updater on top of any previous FCS 1.5.x installation.

The following release notes describe the issues with Flash Communication Server MX 1.5 that are fixed in this release of the Updater, and provide information on installing and uninstalling this Updater.

Contents

NOTE: In these Release Notes,<fcs_install_dir> refers to the directory where Flash Communication Server MX is installed, typically C:\Program Files\Macromedia\Flash Communication Server MX\ in Windows and /opt/macromedia/fcs on Linux.

Flash Communication Server MX 1.5 Issues Fixed in this Release

Flash Communication Server MX 1.5 Updater Release 2 addresses the issues described in the following sections. The following are items have been fixed since Updater Release 1, for a list of issues addressed in the previous hotfix please see the corresponding release notes .

FCS server core issues

Issue
ID
When receive audio/video is set to true message queue is not being cleared causing delay in message delivery.. 66301
Calling send() method on proxy shared objects causing "Bad network data" error. 67797
Client ping returns true if client is in terminated state. 68232

Maximum latency allowed for live audio before the server starts dropping audio msgs is now configurable via a config key in Application.xml

Add the <MsgQueue> block to <Client> section in Application.xml

<Client> <MsgQueue> <!-- Maximum latency allowed for live audio before client starts --> <!-- dropping audio msgs. Specified in msec. This cannot be set --> <!-- to less than 250 msec. Default is 8000 msec. --> <MaxLiveAudioLatency>8000</MaxLiveAudioLatency> </MsgQueue> </Client>
69980
Tunneling failing on legacy proxy servers using HTTP 1.0 protocol. 69374
Server-side streams can cause application instance to abort if a message is sent over a closed stream. 70933
Server-side call to application.getStats() not taking into account tunneling overhead. 72272
JS string objects being prematurely garbage collected when system is under load. 72278
Memory leak if a remote method is invoked with more than 10 args. 72329
Script engine can cause CPU to peg at 100% and never recover. 72331
Potential deadlock in Flash Communication Admin Server if connection to admin server is aborted before admin server completes connection to FCS server. 72869
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. 73034
Memory leak when setting fps (Frames per second) with NetStream.receiveVideo(). 74652
Admin APIs: getUserStats returns wrong values for stream ID's 77257
Admin APIs: getLicenseInfo returns Max_adaptors and Max_vhosts in decimal, should be rounded to integers 77346
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. 78715
JS setInteval not working; timer suddenly stops. 84471
Passing a responder object to a remoting call doesn't work. 84486
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. 84549*
Data and status messages should be caught in the script when valid handlers are setup for the JS Stream object. 84556
When streaming, latency for dropping audio messages changes from 8 seconds to 4 seconds. 84558
For live streaming, server now combines audio samples. This significantly reduces CPU usage when there are lot of subscribers. 84559*
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. 84623
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. 84641
Mime-type for http request is now configurable via a conifg key in Application.xml. 85788*
Component-wise addListener doesn't work 87429
Support recording in FLV 1.1 format.

88412

Fixed slow response problem when calling server-side Stream.length() on corrupted mp3 files.

88398

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. 88649
Server crash in Linux when attempts to load an application where application has syntax error in the server side script 88544
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. 88689
Premature gc of stream can cause crash when calling Stream.get() from server-side script. 88735
Fixed bug in server streaming: On append, messages sent to stream have same time stamp as last message recorded no matter when recorded. 88803
Fixed memory probelm - message pool not being gc'd 89580
Fixed memory problem - dns lookup cache not being gc'd 89581

* Detail TechNotes are provide for bug 84549, 84559 and 85788

Known Issues

  1. On Linux systems, there is known memory leak issue in glibc versions earlier than 2.3.2. Ensure that your system has all the latest updates installed.
  2. Red Hat Enterprise Linux 3 must have the compat-libstdc++-7.3-2.96.126 package installed.

 

Installing the Updater


Installing a Flash Communication Server MX Updater on Windows

  1. Stop the following services: ( Start->Settings->Control Panel->Administrative Tools -> services )
    Flash Communication Admin Service
    Flash Communication Server
  2. Locate the Flash Communication Server MX 1.5 Install directory.
    (Default: C:\Program Files\Macromedia\Flash Communication Server MX\)
  3. Backup the following files:
    Open a DOS window ( Start->Run->Enter "cmd" into the edit field ->Click OK)
    Change directory to <fcs_install_dir> (Flash Communication Server MX 1.5 Install directory):
    cd <fcs_install_dir>
    Create directory fcs_1_5_backup:
    mkdir fcs_1_5_backup
    Backup components and binaries:
    xcopy scriptlib fcs_1_5_backup\scriptlib /s /i
    xcopy *.exe fcs_1_5_backup
    xcopy *.dll fcs_1_5_backup
    xcopy modules fcs_1_5_backup\modules /s /i
  4. Unzip fcs_win_updater_r2.zip file into <fcs_install_dir> directory
  5. Start the following services : (Start->Settings->Control Panel->Administrative Tools > services )
    Flash Communication Admin Service
    Flash Communication Server

Installing a Flash Communication Server MX Updater on Linux

  1. If you already have an existing installation of Flash Communication Server MX 1.5 go onto step 2, otherwise follow these additional steps.
    • Download Flash Communication Server MX 1.5 from http://www.macromedia.com/cfusion/tdrc/index.cfm?product=flashcom
    • Red Hat Enterprise Linux 3 (WS, ES, AS) users need to ensure that compat-libstdc++-7.3-2.96.126 is installed on the system. Please consult Red Hat system administration guide on installing and managing software packages. You should be able to obtain this package from your Red Hat distribution CDs or online from the Red Hat site.
    • Follow the installation instructions that come with Flash Communication Server MX 1.5 distribution. Red Hat Enterprise Linux 3 users will need to pass an additional flag to the installFCS script –
      ./installFCS -platformWarnOnly
    • You are now ready to proceed with the installation of the updater.
  2. Log into the system as root
  3. Change directory to Flash Communication Server MX 1.5 Install directory.
    ( Default /opt/macromedia/fcs)
    CD<fcs_install_dir>
  4. Stop Flash Communication Server MX with the following commands :
    ./fcsmgr server fcs stop
    ./fcsmgr adminserver stop
  5. Backup components and binaries:
    Create directory fcs_1_5_backup:
    mkdir fcs_1_5_backup
    Backup components and binaries:
    cp -rf scriptlib fcs_1_5_backup/
    cp -f fcadmin fcserver fcs_1_5_backup/
    cp -rf modules fcs_1_5_backup/
  6. Run tar commands to uncompress and extract file: fcs_linux_updater_r2.tar.gz into <fcs_install_dir> directory
    This assumes fcs_linux_updater_r2.tar.gz file was downloded into /tmp, if not modify the location appropriately.
    Change directroy to <fcs_install_dir>
    CD<fcs_install_dir>
    Run the tar command to uncompress and extract the fcs_linux_updater_r2.tar.gz
    tar zxf /tmp/fcs_linux_updater_r2.tar.gz
  7. Start Flash Communication Server MX with the following commands :
    ./fcsmgr adminserver start
    ./fcsmgr server fcs start

Uninstalling the Updater

Use the following procedures to uninstall a Flash Communication Server MX 1.5 Updater.

Uninstalling a Flash Communication Server MX Updater from Windows

To uninstall a Flash Communication Server MX updater from Windows:

  1. Stop the following services: ( Control Panel->Administrative Tools > services )
    Flash Communication Admin Service
    Flash Communication Server
  2. Locate the Flash Communication Server MX 1.5 Install directory.
    (Default: C:\Program Files\Macromedia\Flash Communication Server MX\)
  3. Change directory to <fcs_install_dir> (Flash Communication Server MX 1.5 Install directory):
    CD<fcs_install_dir>
  4. Move all of the files in the backup folder for the updater, <fcs_install_dir>\fcs_1_5_backup , to their original locations, replacing the updated files. (The file locations in the backup folder directory tree correspond to their locations relative to the <fcs_install_dir> directory.)
  5. Start the following services : ( Control Panel->Administrative Tools > services )
    Flash Communication Admin Service
    Flash Communication Server

Uninstalling a Flash Communication Server MX Updater from Linux

To uninstall a Flash Communication Server MX updater from Linux:

  1. Log in as root
  2. Change directory to Flash Communication Server MX 1.5 Install directory.
    ( Default /opt/macromedia/fcs)
    CD<fcs_install_dir>
  3. Stop Flash Communication Server MX with the following commands :
    ./fcsmgr server fcs stop
    ./fcsmgr adminserver stop
  4. Move all of the files in the backup folder for the updater, <fcs_install_dir>/fcs_1_5_backup , to their original locations, replacing the updated files. (The file locations in the backup folder directory tree correspond to their locations relative to the <fcs_install_dir> directory.)
    cp -rf fcs_1_5_backup/* ./
  5. Start Flash Communication Server MX with the following commands :
    ./fcsmgr adminserver start
    ./fcsmgr server fcs start

Reporting a bug to the Macromedia Flash Communication Server MX team

Found a bug? Please send the detailed bug information via the online Macromedia Software Feature Request and Bug Report form.

NOTE: Due to the high volume of e-mail we receive, we are unable to respond to every request.

Thank you for using Macromedia Flash Communication Server MX, and for taking the time to send us your feedback!

Top Support Topics

 

More Flash Communication Server Topics

Choose a category to see more topics.

Communication Devices

Request Support

 

Additional Flash Communication Server Resources

 

Flash Communication Server Downloads

 

Feedback

 

Community