Intel® Collaboration Suite for WebRTC
Community support and discussions on the Intel® Collaboration Suite for WebRTC (Intel® CS for WebRTC).
Announcements
Welcome to the Intel Community. If you get an answer you like, please mark it as an Accepted Solution to help others. Thank you!
For the latest information on Intel’s response to the Log4j/Log4Shell vulnerability, please see Intel-SA-00646
1136 Discussions

Session fails when so many users hit the URL

Naresh_R_1
New Contributor I
214 Views

Dear Team,

We are expereancing when many users try to login it fails for some users and have to refresh multiple times for success. does this management API written in sysncronous or asysnchronus since if the users try to connect 1 by one it connects.

 

Thanks

Naresh

0 Kudos
2 Replies
Chandramouli_P
Beginner
214 Views

Hello Intel team,

Good morning and hope you all are doing well. We are also facing the same issues.

Any help would be appreciated.

Thank you.

Best Regards,
Chandramouli P

Naresh_R_1
New Contributor I
214 Views

Hi Team,

 

Below Logs means anything .Because we are facing lots of issues with users logged in. it fails so many times when more users trying to login 

<--- JS stacktrace --->

 

==== JS stack trace =========================================

 

Security context: 0x3d3e6df258b9 <JSObject>

    1: unique [/root/Release-v4.2/management_api/node_modules/mongoose/lib/utils.js:~780] [pc=0x22070189103d](this=0x3cf68c422fe9 <Object map = 0xe8ddc88fd51>,arr=0x2881c6a16059 <JSArray[5010]>)

    2: populate [/root/Release-v4.2/management_api/node_modules/mongoose/lib/model.js:3252] [bytecode=0x1e0f273f3279 offset=340](this=0x357fb1a04f01 <JSGlobal Object>,model=0x3cf68c4680b1 <JSFunction mod...

 

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory

 1: node::Abort() [/usr/local/bin/node]

 2: 0x8cbf6c [/usr/local/bin/node]

 3: v8::Utils::ReportOOMFailure(char const*, bool) [/usr/local/bin/node]

 4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/usr/local/bin/node]

 5: v8::internal::Factory::NewFixedArray(int, v8::internal::PretenureFlag) [/usr/local/bin/node]

 6: v8::internal::HashTable<v8::internal::StringTable, v8::internal::StringTableShape>::NewInternal(v8::internal::Isolate*, int, v8::internal::PretenureFlag) [/usr/local/bin/node]

 7: v8::internal::HashTable<v8::internal::StringTable, v8::internal::StringTableShape>::New(v8::internal::Isolate*, int, v8::internal::PretenureFlag, v8::internal::MinimumCapacity) [/usr/local/bin/node]

 8: v8::internal::HashTable<v8::internal::StringTable, v8::internal::StringTableShape>::EnsureCapacity(v8::internal::Handle<v8::internal::StringTable>, int, v8::internal::PretenureFlag) [/usr/local/bin/node]

 9: v8::internal::StringTable::LookupString(v8::internal::Isolate*, v8::internal::Handle<v8::internal::String>) [/usr/local/bin/node]

10: 0x103340e [/usr/local/bin/node]

11: v8::internal::Runtime_KeyedGetProperty(int, v8::internal::Object**, v8::internal::Isolate*) [/usr/local/bin/node]

12: 0x220700f042fd

2020-04-15 07:52:38.260  - INFO: ManagementServer - Worker 10708 died

2020-04-15 07:52:58.915  - INFO: ManagementServer - Worker 10696 died

2020-04-15 08:07:01.385  - INFO: ManagementServer - Master exiting on SIGTERM

 

Thanks

Naresh

 

Reply