This document was generated from CDN thread
Created by: Angelina Talley on 18-08-2011 01:18:58 PM
We are seeing something very strange in some of the application logs on some CVP Studio apps that have been in production for 18+ months (so not new applications). We had a situation yesterday where the applications got under high load. We saw two very weird things:
1. errors from one application were appearing in the logs of other applications
2. the majority of the errors were basically saying stuff like "com.audium.server.AudiumException: '9_1' is not a valid voice element name". What does this error mean? It's affecting more than one element across multiple apps, and these are not new elements but rather have been in since Go Live
So, my question is this. What could be causing this? Is it a memory problem where apps are stomping on each other's memory? How could that happen? Also, what does this particular error mean given these circumstances? I've never seen it before.
Thanks in advance for any help! Full exception example pasted below.
10.15.2.74.1313602483179.1068881.rogers_core,08/17/2011 13:37:38.977, The error was: '9_1' is not a valid voice element name.
com.audium.server.AudiumException: '9_1' is not a valid voice element name.
at com.audium.server.xml.CallFlow.getVoiceElementClass(CallFlow.java:1005)
at com.audium.server.controller.Controller.goToVoiceElement(Controller.java:2550)
at com.audium.server.controller.Controller.doPost(Controller.java:604)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:834)
at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:640)
at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1286)
at java.lang.Thread.run(Thread.java:595)
Subject: RE: Not a valid voice element name exception
Replied by: Sidney Orret on 18-08-2011 01:32:51 PM
Take a look at the load on the VXML GW. If memory and CPU are maxed out the GW might be having trouble caching audio files or retrieving VXML pages from the VXML server.
Under heavy loads usually the first to suffer are the GW, specially if the voice and vxml are collocated on the same router.
Just a guess at this time.
