" /> Exec out of memory error in MCP logs - Genesys CTI User Forum
« previous next »
Pages: [1]   Go Down

Author Topic: Exec out of memory error in MCP logs  (Read 5197 times)

Offline Prithy

  • Newbie
  • *
  • Posts: 14
  • Karma: 0
Exec out of memory error in MCP logs
« on: February 06, 2016, 12:19:49 PM »
Advertisement
Hi ,

We are getting exec out of memory error in MCP logs. The IVR Composer project is working fine for all the middleware  transaction for the first five mins and then throws this error.

Kindly help urgently how to resolve the same.

Thanks,
Logged

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Exec out of memory error in MCP logs
« Reply #1 on: February 06, 2016, 04:30:14 PM »
Well...can you post logs? Increase server memory? Upgrade to last MCP release???? Something????
Logged

Offline Prithy

  • Newbie
  • *
  • Posts: 14
  • Karma: 0
Re: Exec out of memory error in MCP logs
« Reply #2 on: February 07, 2016, 12:47:31 PM »
Kindly find the logs below. Please help.

9 006C034D-10034212 2243014096 exec_error out of memory
16:18:51.350 Int 50080 006C034D-10034212 2243014096 event_handler_enter :error|http://10.237.152.91:8080/IVR125_Con/src-gen/LandLineMenu.vxml
1998-02-07 16:18:51.350 DBUG 00000000-00000000 6852048 0A000000 Call.cpp:406 processMetric(): got metric exec_error, ts 1998-02-07/16:18:51
1998-02-07 16:18:51.350 DBUG 006C034D-10034212 2243014096 0C000000 CatchRuntime.cxx:131 Execute() Started, event type: -1
1998-02-07 16:18:51.350 DBUG 006C034D-10034212 2243014096 0C000000 CatchRuntime.cxx:148 Execute(): Started
1998-02-07 16:18:51.350 DBUG 006C034D-10034212 2243014096 0C000000 Runtime.cxx:77 RuntimeFactory(): Called for [SimplePrompt] at line [178]
1998-02-07 16:18:51.350 DBUG 006C034D-10034212 2243014096 08500000 SessionConfiguration.C:112 SessConfig::GetValue - Param=[vxmli.conformance.strict_tts_mode]; Value=[FALSE]; [Global]
1998-02-07 16:18:51.350 DBUG 00000000-00000000 6852048 0A000000 Call.cpp:406 processMetric(): got metric event_handler_enter, ts 1998-02-07/16:18:51
1998-02-07 16:18:51.350 DBUG 006C034D-10034212 2243014096 0C000000 SimplePromptRuntime.cxx:33 Execute() Started
1998-02-07 16:18:51.350 DBUG 006C034D-10034212 2243014096 0C000000 Runtime.cxx:77 RuntimeFactory(): Called for [Assign] at line [178]
1998-02-07 16:18:51.350 DBUG 006C034D-10034212 2243014096 0C000000 AssignRuntime.cxx:34 Execute() Started, event type: -1
1998-02-07 16:18:51.350 DBUG 006C034D-10034212 2243014096 0C000000 AssignRuntime.cxx:48 Execute(): Script [AppState.LAST_EVENT_ELEMENT;AppState.LAST_EVENT_ELEMENT=_element;]
16:18:51.359 Int 50039 006C034D-10034212 2243014096 exec_error out of memory
Logged

Offline Prithy

  • Newbie
  • *
  • Posts: 14
  • Karma: 0
Re: Exec out of memory error in MCP logs
« Reply #3 on: February 07, 2016, 12:50:33 PM »
16:18:51.313 Int 50043 006C034D-10034212 2243014096 fetch_end Done (revalidated):http://10.237.152.91:8080/IVR125_Con/include/json.js
1998-02-07 16:18:51.313 DBUG 00000000-00000000 6852048 0A000000 VXMLILog.cpp:69 latency substring is 0ms
1998-02-07 16:18:51.313 DBUG 006C034D-10034212 2243014096 0C000000 VxmlRuntimeRoot.cxx:213 Execute() Started, event type: 1
1998-02-07 16:18:51.313 DBUG 006C034D-10034212 2243014096 0C000000 VxmlRuntimeDoc.cxx:162 Execute() Started, event type: 1
1998-02-07 16:18:51.313 DBUG 006C034D-10034212 2243014096 0C000000 ScriptRuntime.cxx:166 Execute() Started, event type: 1
1998-02-07 16:18:51.313 DBUG 00000000-00000000 6852048 0A000000 Call.cpp:406 processMetric(): got metric 2B68719, ts 1998-02-07/16:18:51
1998-02-07 16:18:51.313 DBUG 00000000-00000000 6852048 0A000000 VXMLILog.cpp:69 latency substring is 13ms
1998-02-07 16:18:51.313 DBUG 00000000-00000000 6852048 0A000000 Call.cpp:406 processMetric(): got metric 2B6871A, ts 1998-02-07/16:18:51
1998-02-07 16:18:51.313 DBUG 00000000-00000000 6852048 0A000000 Call.cpp:406 processMetric(): got metric fetch_end, ts 1998-02-07/16:18:51
16:18:51.332 Int 50039 006C034D-10034212 2243014096 [b]exec_error out of memory. Line 1[/b]
1998-02-07 16:18:51.332 DBUG 00000000-00000000 2243014096 08500500 VGDocumentManager.cxx:364 Deleting document, uri: http://10.237.152.91:8080/IVR125_Con/include/json.js
1998-02-07 16:18:51.332 DBUG 006C034D-10034212 2243014096 08500000 SessionConfiguration.C:112 SessConfig::GetValue - Param=[vxmli.maintainer.log_message.on_error]; Value=[TRUE]; [Global]
1998-02-07 16:18:51.332 DBUG 006C034D-10034212 2243014096 0C000000 SemanticError.cxx:22 SemanticError() Created error.semantic from element: [Script] at line number: [16] with message: [out of memory. Line 1]
1998-02-07 16:18:51.332 DBUG 006C034D-10034212 2243014096 0C000000 ScriptError.cxx:9 Created error.semantic from element [Script] at line number [16] from script [http://10.237.152.91:8080/IVR125_Con/include/json.js]
1998-02-07 16:18:51.332 DBUG 00000000-00000000 6852048 0A000000 Call.cpp:406 processMetric(): got metric exec_error, ts 1998-02-07/16:18:51
16:18:51.332 Int 50034 006C034D-10034212 2243014096 event error.semantic:1|out of memory. Line 1
Logged

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Exec out of memory error in MCP logs
« Reply #4 on: February 07, 2016, 04:40:43 PM »
Does MCP crashes or just the application execution?  ???
Seems there is some sort of error or memory execution control on your VXML code.

Try to check the Tomcat logs to see HTTP handling

Logged

Offline Prithy

  • Newbie
  • *
  • Posts: 14
  • Karma: 0
Re: Exec out of memory error in MCP logs
« Reply #5 on: February 08, 2016, 07:08:44 AM »
Hi ,

yes the mcp crashes sometimes. The tomcat logs are fine. Kindly find the below MCP logs., after this the call is blank.

10:47:31.977 Int 50028 006C034D-10034777 2241035728 form_enter
1998-02-08 10:47:31.977 DBUG 00000000-00000000 6241744 0A000000 Call.cpp:406 processMetric(): got metric form_enter, ts 1998-02-08/10:47:31
1998-02-08 10:47:31.977 DBUG 006C034D-10034777 2241035728 0C000000 Runtime.cxx:77 RuntimeFactory(): Called for [Var] at line [97]
1998-02-08 10:47:31.977 DBUG 006C034D-10034777 2241035728 0C000000 VarRuntime.cxx:37 Execute() Started, event type: -1
1998-02-08 10:47:31.977 DBUG 006C034D-10034777 2241035728 0C000000 Runtime.cxx:77 RuntimeFactory(): Called for [Var] at line [99]
1998-02-08 10:47:31.977 DBUG 006C034D-10034777 2241035728 0C000000 VarRuntime.cxx:37 Execute() Started, event type: -1
1998-02-08 10:47:31.977 DBUG 006C034D-10034777 2241035728 0C000000 Runtime.cxx:77 RuntimeFactory(): Called for [Var] at line [100]
1998-02-08 10:47:31.977 DBUG 006C034D-10034777 2241035728 0C000000 VarRuntime.cxx:37 Execute() Started, event type: -1
1998-02-08 10:47:31.977 DBUG 006C034D-10034777 2241035728 0C000000 Runtime.cxx:77 RuntimeFactory(): Called for [Var] at line [101]
1998-02-08 10:47:31.977 DBUG 006C034D-10034777 2241035728 0C000000 VarRuntime.cxx:37 Execute() Started, event type: -1
1998-02-08 10:47:31.977 DBUG 006C034D-10034777 2241035728 0C000000 Runtime.cxx:77 RuntimeFactory(): Called for [Var] at line [102]
1998-02-08 10:47:31.977 DBUG 006C034D-10034777 2241035728 0C000000 VarRuntime.cxx:37 Execute() Started, event type: -1
1998-02-08 10:47:31.977 DBUG 006C034D-10034777 2241035728 0C000000 Runtime.cxx:77 RuntimeFactory(): Called for [Var] at line [103]
1998-02-08 10:47:31.977 DBUG 006C034D-10034777 2241035728 0C000000 VarRuntime.cxx:37 Execute() Started, event type: -1

Do we need to modify in exception handling of each callflow. Currently we have error.badfetch,error.semantic,disconnect hangup, error , all.
Logged

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: Exec out of memory error in MCP logs
« Reply #6 on: February 08, 2016, 08:53:32 AM »
Try to optimize your vxml app in case having a lot of subdialogs. In other cases you can tune your MCP instance through following options:

[list]
[li][vxmli]jsruntime_size[/li]
[li][vxmli]jsstack_size[/li]
[/list]

Of course, you should follow the release notes and delpoy to latest version of MCP.
Logged

Offline Prithy

  • Newbie
  • *
  • Posts: 14
  • Karma: 0
Re: Exec out of memory error in MCP logs
« Reply #7 on: February 08, 2016, 12:24:49 PM »
Hi Kubig,

Kindly help us how to upgrade the MCP. Kindly share the steps.

Thanks,
Logged

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: Exec out of memory error in MCP logs
« Reply #8 on: February 08, 2016, 12:31:18 PM »
[list type=decimal]
[li]Make a backup of current configuration[/li]
[li]Make a backup of non-default folders and configuration files under MCP install folder - like announcement, defaults-ng.vxml, etc[/li]
[li]Stop the MCP[/li]
[li]Change the app template and read the configuration from the template[/li]
[li]Restore your configuration from the backup[/li]
[li]Upgrade MCP binaries[/li]
[li]Start MCP[/li]
[/list]

Strongly recommend to learn about GVP before make some "drastical" steps. It is not good to make anything without sufficient knowledges. Another recommendation was provided before, try to optimize the mentioned options which affect the MCP performance related to processing huge JS or VXML in general.
« Last Edit: February 08, 2016, 12:42:53 PM by Kubig »
Logged

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Exec out of memory error in MCP logs
« Reply #9 on: February 08, 2016, 07:22:41 PM »
O.o you need a Genesys guy on site buddy...if you can't do a simple upgrade how you can provide support? And worst...test correctly your GVP behavior. Project at risk on eye
Logged

Offline Prithy

  • Newbie
  • *
  • Posts: 14
  • Karma: 0
Re: Exec out of memory error in MCP logs
« Reply #10 on: February 09, 2016, 05:42:37 AM »
Many Thanks Kubig for the steps. We will definitely take help from a Genesys guy and understand the upgrade steps. We will look for options to optimize.  We are currently using 8.1.310.08 MCP version. Can a MCP upgrade control the issue of call getting blank after 7-8 transactions ?

Thanks Cavagnaro.
Logged

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: Exec out of memory error in MCP logs
« Reply #11 on: February 09, 2016, 08:44:11 AM »
Just note: Be aware, if you are using LGVP interpreter for processing VXML. This interpreter is available just to the version 8.1.4 and not higher.
Logged
Pages: [1]   Go Up
« previous next »