Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

com.adobe.rtc.util.RTCError: not-active (on our production environment)

Avatar

Level 2

Hi,

We have the following error "com.adobe.rtc.util.RTCError: not-active" on all our environment (3 different LCCS accounts), including our production environment. This is a new error that we were not having before. We had successfull video conference in the past weeks, and our code base didn't change for months.

Here is the code generating the error:

AccountManager accountManager = getAccountManager();

accountManager.createRoom(room, "HHConference");

MessageItem item = new MessageItem("item", conferenceMode.getValue(), "item");

accountManager.publishItem(room, "roomMode", "value", item, true);

The "room" variable is the room name composed of lowercase alphanumeric characters (max 21 characters)

The template name is "HHConference" ... Is it a problem to have capital letters in the template name?

The "conferenceMode.getValue()" returns the integer "7".

Is there anything that change on your side that could explain this error?

Fast help would be appreciated, as we have a demo this friday.

Thank you very much!

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Servers are back up. Service is back to normal.

We are really sorry for the inconvenience.

We will post more info in a little bit on what went on.

Thanks,

Julien

LCCS Quality Engineering team

View solution in original post

3 Replies

Avatar

Former Community Member

Hi Matetnic,

Thanks for the post.

The team is actively working on solving a problem with our Production environment (it looks like its related to our FMS servers - we will know more shortly).

We will update the forums in a few when everything is back to normal.

We posted the problem on our health page:

http://health.acrobat.com/

Best,

Julien

LCCS Quality Engineering team

Avatar

Level 2

Thanks for your quick answer.

We'll stay tuned for an update.

Avatar

Correct answer by
Former Community Member

Servers are back up. Service is back to normal.

We are really sorry for the inconvenience.

We will post more info in a little bit on what went on.

Thanks,

Julien

LCCS Quality Engineering team

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----