Macromedia Flash Media Server 2.0.5 Release Notes
Welcome to the Macromedia Flash Media Server 2.0.5 release! This document contains latebreaking product information and updates concerning this release. About Flash Media Server 2.0.5 System requirements What's New in Flash Media Server 2.0.5 Known Issues Documentation Updates Reporting a bug to the Flash Media Server team Notices, Terms, Conditions, and Attribution
About Flash Media Server 2.0.5 This update to Flash Media Server 2.0 provides a number of key bug fixes. Adobe recommends that you install this update if you are currently using Flash Media Server 2.x. You can also check out the many resources available for learning about Flash Media Server at the Flash Media Server Developer Center. Find inspiration with tips, articles, tutorials, and resources, or steer your project to success with forums, code examples, exchanges, and reference materials. System Requirements Flash Media Server 2.0.5 is supported on Microsoft Windows 2003 Server, Microsoft Windows 2000 Server, Linux Red Hat Enterprise 3.0, and Linux Red Hat Enterprise 4.0. For more information, please see the Flash Media Server 2 system requirements. What's New in this Release The following bugs have been fixed in this release: 1481331 A deadlock could occur when performing garbage collection of live streams. A deadlock could occur when generating thumbnails with live streams. A DOS attack caused by sending bad data to the server which resulted in huge memory allocations has been prevented. When garbage data sent to the server it could result in a buffer overrun. This has been prevented. The performance of disk caching on Edge servers has been improved. The server could get into an infinite loop when playing large (~900 MB) MP3 files. On Linux, the FMS Edge process could crash when making an RTMP connection to a secure port.
Known Issues The following issues were known to exist at the time of the release. These issues are in addition to any listed elsewhere.

1453454 1440015

1437150

1431369

Edge process memory can grow significantly when using RTMPT or RTMPS (tunneled), resulting in a crash. Status is set as NetStream.Clear.Success when Streams.clear() method is invoked on a pre-recorded.flv file that has read-only permissions. The <OutChunkSize> configuration does not result in the same performance gains for On2 live video as it does for Sorenson live video. In server-side ActionScript, NetConnection.onStatus always returns NetConnection.Connect.Success when attempting a remoting connection (i.e., an HTTP url instead of RTMP), even if the url is invalid. When xml.sendAndLoad() is used the xml.loaded stays false even when XML is downloaded successfully and the onLoad event handler is invoked. The workaround is to set this to true in the onLoad handler when you know it has been loaded. unloadApp admin API takes a long time to return when the specified application instance doesn't exist. When true is passed as the parameter for the FileObject.remove method it does not recursively remove all the files in the folder. Streams greater than 2 GB are not supported.
Documentation Updates In the Flash Media Server 2 Server Management ActionScript Language Reference manual, on page 37, the properties for the getLicenseInfo() data object have changed. The key, type, family, and edition properties are no longer available. A new license_files object containing information about license files has been added. In the Flash Media Server 2 Server Management ActionScript Language Reference manual, on page 42, the properties for the getNetStreamStats() data object have changed. A new client_type property has been added. Different types of clients include the following: normal clients (clients connected directly to the origin server through Flash player), group clients (edge servers connected to the origin), virtual clients (clients connected through an edge to the origin) and service clients (clients connected to the service application). In the Flash Media Server 2 Server-Side ActionScript Language Reference manual, on page 115116, one of the methods used to invoke setInterval() is no longer valid. The first method, setInterval(function, interval[, p1, , pN]) is correct and should be used. The second method, setInterval (object, methodName, interval[, p1, , pN]) is not valid. In the Flash Media Server 2 Server-Side ActionScript Language Reference manual, the usage description for Stream.setVirtualPath() on page 158 is incorrect. The statement should read: Stream.setVirtualPath(virtual Path, directory, virtualKey). Viewing documentation updates using LiveDocs In addition to accessing Flash Media Server documentation in the Flash Help panel, you can access the same documentation online in the LiveDocs format. One of the advantages of LiveDocs is the ability to see comments that clarify the documentation. Macromedia recommends reviewing LiveDocs to see if any errata or issues relating to the Flash Media Server features you are using have been reported. To find the equivalent page on the LiveDocs website, click the View Comments on LiveDocs link at the bottom of any help page in the Flash Help panel. Your web browser will launch, and take you to the specified LiveDocs page.

The Flash Media Server LiveDocs are available at: http://www.adobe.com/go/flashmediaserver_help_en Reporting a bug to the Flash Media Server Team Found a bug? Your first step should be to contact Macromedia Technical Support. They can help you resolve issues and they can also log bugs. If you are no longer eligible for support, please use the Software Feature Request and Bug Report form. In order for us to understand the issue being reported please include every detail possible, including the operating system details, CPU, memory, crash log (if applicable). We will get back to you when the issue you reported has been verified. Thank you for using Macromedia Flash Media Server, and for taking the time to send us your feedback Notices, Terms, Conditions, and Attribution Copyright 1993-2008 Adobe Systems Incorporated and its licensors. All Rights Reserved. Macromedia, the Macromedia logo and Flash are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Other marks are the property of their respective owners. Protected by U.S. Patents. Patents pending in the U.S. and/or other countries. This computer program is protected by copyright law and international treaties. Unauthorized use, reproduction, or distribution of this program, or any portion of it, may result in severe civil and criminal penalties, and will be prosecuted to the maximum extent possible under the law. Notices, terms and conditions pertaining to third party software are located at http://www.adobe.com/go/thirdparty/ and incorporated by reference herein.

AdobeFlashMediaServer3.0.2Update ReleaseNotes
WelcometotheAdobeFlashMediaServer3.0.2Updaterelease!Thisdocumentcontainslatebreaking productinformationandupdatesconcerningthisrelease. Minimumsystemrequirements Installyoursoftware Uninstallyoursoftware What'snewinthisrelease Knownissues Otherresources ThisupdateofFlashMediaServer3.0.2.217replacesthepreviouslyreleased3.0.2.210version,and improvestheperformanceofH.264streaming,includingfurtherperformanceenhancementsandgarbage collectiontohelppreventbuildupofmemoryusage.Specificallytherehasbeenoptimizationthat improvesthememoryusagewhenyouplaybacklargeH.264files.
Adobe encourages you to install this update to ensure that you have the most updated version of Flash Media Streaming Server 3.0.2 or Flash Media Interactive Server 3.0.2.
Minimumsystemrequirements TheFlashMediaServer3.0.2Updatesystemrequirementsforproductionenvironmentsare: OS Version Memory Processor Microsoft WindowsServer2003SP1 2GBminimum, 3.2GHzIntelPentium4 Windows (All32biteditions) 4GBrecommended processor(dualIntelXeonor fasterrecommended) Linux RedHat4 2GBminimum, 3.2GHzIntelPentium4 32bitonly 4GBrecommended processor(dualIntelXeonor fasterrecommended) TheFlashMediaServer3.0.2Updatesystemrequirementsfordevelopmentenvironmentsare: OS Version Memory Processor Microsoft WindowsXPSP2 1GB 1GHzIntelPentium4 Windows processororfaster Installyoursoftware ToinstallFlashMediaServeronWindows: 1. Doubleclicktheinstallerapplicationandfollowtheonscreeninstructions. 2. Enteraserialnumber.Ifyoudontenteraserialnumber,FlashMediaDevelopmentServer installs.
3. Duringtheinstallationprocessyouwillbeaskedtoenterausernameandpasswordforthefirst validserveradministrator.Thesevaluesarewrittentothefms.inifilewhichislocatedintheconf folderafterinstallation.(YoucanusetheAdministrationConsoletoaddotheradministrators later.) Acceptthedefaultserverportsorenternewportnumbers. ThefinalinstallationstepgivesyoutheopportunitytoviewtheReadme.htmfile,startFlash MediaServer,andselecttheoptiontostartFlashMediaServermanuallywhenyourebootyour computer.Selectanyoptionsyou'dlike,andclickFinish.

4. 5.

Theinstallationiscomplete.Ifyouconfiguredittostartautomatically,theFlashMediaServerservice starts.Tostarttheservermanually,selectStart>Programs>Adobe>FlashMediaServer3>StartAdobe FlashMediaServer3andStartFlashMediaAdministrationServer3. ToopentheFlashMediaAdministrationConsole,selectStart>Programs>Adobe>FlashMediaServer3 >FlashMediaAdministrationConsole. ToinstallFlashMediaServeronLinux: 1. Loginasarootuser(requiredtoinstallFlashMediaServer). 2. Openashellwindowandswitchtothedirectorywiththeinstallationfile, FlashMediaServer3.tar.gz 3. Unzipanduntartheinstallationfile.Adirectorywiththeinstallationprogramiscreated. 4. Switchtothedirectorythatwasjustunzipped. 5. Starttheinstallationprogramwiththefollowingcommand:./installFMS 6. Theinstallationprogramstartsanddisplaysawelcomemessage. 7. PressEntertostarttheinstallation.Followtheinstallationinstructionsonyourscreen.During theprocessyouwillbeaskedto 8. Enteraserialnumber.Ifyoudontenteraserialnumber,FlashMediaDevelopmentServer installs. 9. Entertheinstallationdirectoryandportswhichtheserverwilluse 10. Enteranadministrativeusernameandpasswordforthefirstvalidserveradministrator.These valuesarewrittentothefms.inifilewhichislocatedinsideoftheconffolderafterthe installation. 11. EnterauserforFlashMediaServerprocessestorunas.Thedefaultisthe"nobody"user.(The useryouselectisalsotheowneroftheFlashMediaServerfiles.)Yourchoicesarewrittentothe fms.inifile.Youcaneditthefms.inifiletomodifythisandothersecuritypropertieslater,if needed. 12. Reviewthesummaryoftheinstallationoptionsyouhavechosen,whicharedisplayedinthe installer.

13. Tostarttheservermanually,gototheinstallationdirectory(defaultis/opt/adobe/fms/).Usethe command./fmsmgrserverstarttostartFlashMediaServerand./fmsmgradminserverstartto startFlashMediaAdministrationServer. Theinstallationiscomplete.Ifyouconfiguredittostartautomatically,theFlashMediaServerservice starts. Uninstallyoursoftware TouninstallFlashMediaServerfromaWindowscomputer: 1. SelectStart>Programs>Adobe>FlashMediaServer3>UninstallAdobeFlashMediaServer3 2. Intheconfirmationdialogbox,clickYestouninstallFlashMediaServer. 3. FlashMediaServerisremovedfromyourcomputer.Asecondconfirmationdialogboxappears whentheprocessiscomplete. TouninstallFlashMediaServerfromaLinuxcomputer: 1. LogontotheserverwhereFlashMediaServerwasinstalled. 2. Switchtotherootuser,orauserwithrootpermissions.Normallyyouwouldusesurootto switchtotherootuser. 3. AttheUNIXshellprompt,entercd/opt/adobe/fms. 4. Bydefault,/opt/adobe/fmsisthedirectorywhereFlashMediaServerisinstalled.Ifyouinstalled theserverinadifferentdirectory,replace/opt/adobe/fmswiththeactualinstallationlocation. 5. Executetheuninstallscript./uninstallFMS. 6. Followthedisplayeduninstallinstructions. What'snewinthisrelease Thefollowingbugsarefixedinthisrelease: LivestreamingthroughanEdgeservercouldexhibitalonginitialpause.Thiswasdueto 1827394 theserverfailingtoresetcertaincounterswhenthenumberofsubscribersdroppedto zeroandwentbackup. TheservercreatedanunboundednumberofthreadswhenhandlingSSLconnectionson 1815838 Windowsplatform. FLVfileobjectswerenotbeinggarbagecollectedcorrectly,resultinginaslowmemory 1809797 leakandeventuallyacoreprocesscrash. KnownIssues Thefollowingissueswereknowntoexistatthetimeofrelease:

1656058

1631225

1630621 1630008

1628134 1626125

1622396

1525751

1322937

SSASXMLclassincorrectlyinterpretsBOM(ByteOrderMark)inafileasanxmlnode. RegisteringverylargeSWFs,thosearoundorinexcessof1GigaByteinsize,forSWF Verification,cancausetheservertoexhaustavailablememory. Theserverbehaviorisnotguaranteedwhenstreamingcorruptedfiles,especiallythose containingH.264/AACcontent,andmayresultinissuesrangingfromsevereperformance degradation,excessivememoryusageandpossiblyserverprocesscrashes.Pleaseuse FLVChecktooltoensurecontentintegritybeforeitisdeployed. Whenplayingaserversidestream,aminimumbufferTimemustbesetontheclientsideto ensuresmoothplayback. Whenplayinganmp3,the.mp3fileextensionshouldnotbeincludedinthestreamname WhenupgradinganFMS2EdgeservertoFMS3,youshouldnotattempttousemediacache filesgeneratedbythepreviousserverversion.Anyexistingcachefilesshouldbecleared beforeusingFMS3asanEdgeserver. VerylowframerateH264videosmaytakealongtimetostartifthebufferissettooshort. PausecommandinFlashPlayer9.0.115orlaterversionswillnotsuspendthebufferfrom gettingfilled.Iftheplaybackisresumedbeforethebufferisfull,pauseandunpauseevents willnotbeloggedintheserversaccess.log. RecordingH.264contentontheserverisnotsupportedinthisversion. Whentheserverisoverloaded,itcanresultinnonpagedpoolmemorybeingexhausted leadingtoinstabilitywhichmayrequirerebootingthesystem(notjustrestartingFlash MediaServer).Formoreinformationonthisnonpagedpoolspike,pleasesee http://support.microsoft.com/kb/931311. LiveAggregateMessagesfeatureenableshigherperformancelivestreamingbutis incompatiblewithcollapsingaudiomessages.HenceAudioCollapseshouldbedisabledin thissituation. TheOnImageDatainH264streamsisnotsupportedinthisversion. Serversideplaydoesnotplayifthefilesizeislessthantheconfiguredbuffertime (MinBufferTimetaginApplication.xml),or2seconds. WhileusingAMF0modewithAS3,IfDate(orXML)isbeingpassedasanargumentinaRMI (NetConnection.call,NetStream.sendorSharedObject.send),thenitshouldbepassedasthe lastargument.Morespecifically,noargumentshouldbesentasreferenceafteraDateor XMLhasbeenaddedtotheargumentlistofanRMI.UsingAMF3withAS3isrecommended. UseMicrosoft.NET2003orMicrosoftVisualC++2005tocompileadaptorsonWindows. UseGNUCompilerCollection3.4.xtocompileadaptorsonLinux.

Otherresources FlashMediaServerDocumentationCenter FlashMediaServerProductHome FlashMediaServerDeveloperCenter FlashMediaServerEndUserLicenseAgreement FlashMediaServerOnlineForums FlashVideoStreamingService FlashMediaSolutionsProviders FlashPlayerProductHome
Copyright2008AdobeSystemsIncorporated.