Live streaming stops automatically after 15 minutes

Question

I am using flash media server 3 and flash media encoder 2.5.
From media encoder I am sending data to media server and then in
browser I am running flex application (version 3) to view the live
stream. I am not saving it in flv file. After 15 mintues live
streaming stops automatically. I have tested all events related to
it..but none of them executes..Flex3 application is just working as
a client.
Portion of code:
nc.connect ("rtmp://localhost/myLiveApp/instance1/");
vid.attachNetStream (ns);
ns.play("flv:mylivestream");
case "NetStream.Play.StreamNotFound" :
/*The FLV passed to the play() method can't be found. */
mx.controls.Alert.show("stream not found");
break;
code in main.asc file :
application.onAppStart = function()
// generate random payload used in bw detection
this.payload = new Array();
for (var i=0; i<1200; i++){
this.payload
= Math.random(); //16K approx
application.onConnect = function(p_client, p_autoSenseBW)
//Add security here
//p_client.writeAccess = ""; // prevents creating shared
object or live streams.
this.acceptConnection(p_client);
p_client.audioSampleAccess = "/";
p_client.videoSampleAccess = "/";
if (p_autoSenseBW)
this.calculateClientBw(p_client);
else
p_client.call("onBWDone");
Client.prototype.getStreamLength = function(p_streamName) {
return Stream.length(p_streamName);
Client.prototype.checkBandwidth = function() {
application.calculateClientBw(this);
application.calculateClientBw = function(p_client)
var res = new Object();
res.latency = 0;
res.cumLatency = 1;
res.bwTime = 0;
res.count = 0;
res.sent = 0;
res.client = p_client;
var stats = p_client.getStats();
var now = (new Date()).getTime()/1;
res.pakSent = new Array();
res.pakRecv = new Array();
res.beginningValues = {b_down:stats.bytes_out,
b_up:stats.bytes_in, time:now};
res.onResult = function(p_val) {
var now = (new Date()).getTime()/1;
this.pakRecv[this.count] = now;
trace("** onResult this.count = " + this.count + " :
this.sent " + this.sent);
//trace( "Packet interval = " + (this.pakRecv[this.count] -
this.pakSent[this.count])*1 );
this.count++;
var timePassed = (now - this.beginningValues.time);
if (this.count == 1) {
this.latency = Math.min(timePassed, 800);
this.latency = Math.max(this.latency, 10);
//trace("count = " + this.count + ", sent = " + this.sent +
", timePassed = " + timePassed);
// If we have a hi-speed network with low latency send more
to determine
// better bandwidth numbers, send no more than 6 packets
if ( this.count == 2 && (timePassed<2000))
this.pakSent[res.sent++] = now;
this.cumLatency++;
this.client.call("onBWCheck", res, application.payload);
else if ( this.sent == this.count )
// See if we need to normalize latency
if ( this.latency >= 100 )
{ // make sure we detect sattelite and modem correctly
if ( this.pakRecv[1] - this.pakRecv[0] > 1000 )
this.latency = 100;
// Got back responses for all the packets compute the
bandwidth.
var stats = this.client.getStats();
var deltaDown = (stats.bytes_out -
this.beginningValues.b_down)*8/1000;
var deltaTime = ((now - this.beginningValues.time) -
(this.latency * this.cumLatency) )/1000;
if ( deltaTime <= 0 )
deltaTime = (now - this.beginningValues.time)/1000;
var kbitDown = Math.round(deltaDown/deltaTime);
trace("onBWDone: kbitDown = " + kbitDown + ", deltaDown= " +
deltaDown + ", deltaTime = " + deltaTime + ", latency = " +
this.latency + "KBytes " + (stats.bytes_out -
this.beginningValues.b_down)/1024) ;
this.client.call("onBWDone", null, kbitDown, deltaDown,
deltaTime, this.latency );
res.pakSent[res.sent++] = now;
p_client.call("onBWCheck", res, "");
res.pakSent[res.sent++] = now;
p_client.call("onBWCheck", res, application.payload);
What is the problem? From media server console I can see 2
connection for 15 minutes and after that it drops to 1.
I have tested it with medium and low bandwith.
Any help is appreciated.

Answer 1

Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.
Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.