Strobe does not recover from incorrect bitrate measurement

Question

While doing some testing of dynamic Flash streaming on low bandwidth devices I found a scenario where Strobe gets stuck trying to switch to the highest bitrate stream when there is not enough bandwidth.  I have a video showing what happens at the link below:
http://www.youtube.com/watch?v=7n_sFH6aYj4
What you will see in the video is the Strobe debug player viewing dynamic Flash streams with bitrates from 200Kbps to to 3000Kbps on the traditional Akamai Flash network.  The computer has a bandwidth limiter enabled limiting the download bandwidth to 1000Kbps and in the video you will see a system monitor showing the network history.  Basically what happens is the download bandwidth (averageDownloadKbps) being measured by the player jumps to around 156000Kbps thus fooling the player into trying to switch to the 3000Kbps stream, but there is not enough actual bandwidth to play that stream.  Then the player ends up in a continuous buffering state trying to make the switch.
It should be mentioned that with OVP the incorrect download bandwidth measurement occurs as well, but OVP seems to have a failsafe in its switch algorithm that uses a near empty buffer to override the download measurements for switching and force a switch the lowest bitrate.
Note, I still need to discuss why this is happening with Akamai.  This should be a corner case that we never see.
Tim

Answer 1

Hi,
1) Try to refresh the metadata
2) Check the Queue status
3) Once again check the Queue name. try to make the Sender JMS adapter inactive .save  it..again make it active  and  save it and  activate the object.
4) Refresh the Cache :
a)Start transaction SXI_CACHE.
b)From the context menu XI Runtime Cache select Start Complete Cache Refresh.
If you still face issue try this .
Many actions require to access System Landscape Directory content from the Integration Builder. To optimize performance, this content is loaded into a cache so that the System Landscape Directory does not have to be accessed directly each time that System Landscape Directory content is required.
However, this cache is not automatically updated if changes are made to the content of the System Landscape Directory. For this reason that we delete the System Landscape Directory cache if changes have been made to content in the System Landscape Directory. The cache is then filled each time that the System Landscape Directory is accessed. If we log on to the Integration Builder after we have made a change in the SLD, we do not need to delete the SLD cache.
To clear the SLD cache, from the Integration Builder main menu, choose Environment ® Delete Cache for SLD Data.
Once we have deleted the cache for SLD data, accessing objects in the SLD may take longer than usual initially.
Regards
Agasthuri Doss