Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: Ricky on September 12, 2017, 04:59:20 AM
-
Hi All,
We are getting java out of memory error many times which is causing performance issue on call back. Current memory of the JVM is 512 MB(32 Bit).
Can any one advise that increasing the JVM memory can help in this issue. Below is the UCS logs-
UCS Log:
11:08:48.372 Trc 29998 [Notifier-1] index.contact Event 0000Ca8CH6VK00JD@Tue Sep 05 11:06:15 EST 2017 [update] ContactAttribute: StrValue=(String)|TenantId=(Integer)101|Description=(String)""|AttributeName=(String)"LastCalledAgent_EmployeeID"|Id=(String)"0000Ca8CH6VK00JD"|ContactId=(String)"0000Ca8CH6VK00H1"|IsPrimary=(Boolean)true|AttributeId=(String)"00001a8A9N0B000V"
11:08:48.372 Dbg 29999 [Notifier-1] End Notification 11405
11:08:48.372 Dbg 29999 [SvcSrvW-675] <2385702 txn-2564467 txn-2564467> Released connection (23148983@txn-txn-2564467) to pool
11:08:48.372 Dbg 29999 [SvcSrvW-675] <2385702 txn-2564467 txn-2564467> Transaction duration: 187066 ms (2564467)
11:08:48.372 Std 20121 [SvcSrvW-675] <2385702> Service 'OMInteractions' failed in method 'GetInteractionsForContact' (Java heap space).
java.lang.OutOfMemoryError: Java heap space
11:08:48.387 Trc 21001 [SvcSrvW-675] <2385702> Service 'OMInteractions' method 'GetInteractionsForContact' ended, processing time (ms): 187081.
11:08:48.387 Std 21130 [SvcSrvW-675] Exception : Java heap space.
java.lang.OutOfMemoryError: Java heap space
-
Increasing of the memory will fix just the symptom of the issue (the out of memory issue), but you still need to find why the memory is allocated to much - it might be caused by incorrect sizing, wrong archiving, slow responses from RDBMS, missing indexes, etc. Strongly recommend to look for root-cause, not just increase the memory.
-
512 M is very little for UCS...
The latest 8.5 versions of UCS has 2048 M dedicated in the ContactServer.ini file if I remember correctly
-
Agree, UCS consumes a lot by default, previous was 1024, now increased to 2048.
If issue happens again at 2048 check what kubig suggests, fix the root problem.