Automatic kill switch?

[daminee80]

I am doing some testing currently, where I leave the service on over night with no user intervention. However after a few hours it seems to close the streems. I am not sure if this a feature of LCCS, and if it is, is there anyway I can adjust this?

[Former Community Member]

There shouldn't be a kill-switch, unless you run over the quota limit. Is

that possibly the case? Check the developer portal and see how the pie chart

looks.

nigel

[daminee80]

I am on a paid account, and I have a lot of pie left.Should it matter on what mode I have it set on? hub-and-spoke, p2p?

[daminee80]

I tested it once more, after about 6 hours or so, it seems to cut off

[Raff_]

Are you saying you have users connected to a room, but the room terminates after a while ?

Normally rooms "shut down" a few minutes after all users have left, but they stay running as long as there are users connected.

If you still think you have a problem you should send us the room URL and the approximate time of when you think the rooms ends (or at least the time of the last user activity you think you had) and we can try to look at our logs and see if there is anything strange going on.

[daminee80]

Can I send you my room info my email?

[Raff_]

Send the info to lccs@adobe.com or send me a private message (click on my icon and there should be a "Send Private Message" in the Action box on the right side of the screen)

[daminee80]

I sent you an email... thanks again

[Raff_ · Accepted solution]

Ok, sorry for the delay but I had a bunch of things on my plate

So, it turns out there is an "automatic kill switch". I look at the logs for your application and here it is. We have a "timer" called "doTwelveHoursDisconnect" and guess what that does ?

I think this was added in the good old days when the only application running was our online meeting application, and we thought nobody would ever run a meeting for more than 12 hours (and we wanted to make sure we could stop rooms getting stuck).

Now, I understand that with the service open to any kind of applications you can think of there may be cases for room that runs for days at once so we'll have to think of how correctly manage this. Maybe we should add RoomManager configuration item that will allow to set your room to never be killed if there are active users in it, but again for now you should understand that rooms are killed after 12 hours.

[daminee80]

NP, Thanks for the reply^^ doTwelveHoursDisconnect, that might be a hard one to figure out... that's why you should leave good comments next to all your variable names^^ Sorry for the bad joke... But yeah, I figured something was strange, because it seemed to take the same amount of time to cut off everyday. One possible case of a room, (which I thought about implementing) Actually,  that comes to mine would be a security monitoring program. Something like that might have to be on 24/7 (hopefully). It might be helpful, if paying members could turn that feature off.