Hi Ross, thank you for clarifying that. After I did that change, I noticed that my IVR is now up and running for almost 20hours without downtime because before I am getting an out of memory time to time.

Uhmm, yeah, hahaha, the reason being is that the client has several changes every now and then, adjusting timezone on the callflow, new spiels, delete this delete that add this add that. Too many appends :) I was surprised that it also surprised you :). Nevertheless, my question is that if it's now okay to use Experience Portal as my runtime platform after I changed it from Desktop.

Hi Ross, just to clarify, I won't be deploying my project as a war file. So my question is, what would be the project properties for the runtime platform of my callflows? Thanks

Hi Ross, Have reviewed what you've said and you we're right, it was set to desktop, so I changed it to EPMS (Experience Portal).
Since I'm using Experience Portal 7.0, I assume EPMS will be also my runtime platform. Also, after I changed it, i noticed a tons of logs on the console when the IVR gets a call. Please see attached image. Thank you much again, i will monitor the server.

Hi ross, apologies for that. I' somehow frustrated with the issue. I will check this one. I'll try to re-export the callflow.
Would you mind checking my attachment? I just want to confirm if this is the one you are pertaining to.
*Edited: just added the web.xml file.

Hi Ross, that is exactly I'm looking for and I can't explain it by myself. I just attached the thing I did on the approot that seems not sufficient enough. Honestly speaking, I don't know how to catch vxml events.

Hi Ross, I added java.net.ConnectException in the Approot of my main callflow to properly disconnect the caller when it hangs-up in the middle. Would that be sufficient enough?

Hi Ross, as of the moment there is an Avaya SR ticket going through and we haven't seen it yet. May I know what web.xml file are you referring to and where can I possibly find it. Hoping for your response :) Thanks!

Hi, may I know if Exit or endcall would be enough to properly disconnect the caller? Is this sufficient enough to lower the use of tomcat memory and threads? I noticed on my callflow that I am using only endcall to prompt thank you to the caller then that's it. Is there a proper way to disconnect the caller or even the caller drops the call? Thank you!

Hi All, this is bugging me and our client right now. I need further assistance on this. I noticed that my tomcat and my eclipse environment is pointed to JDK, so what I did is to point it on JRE7. Restarted eclipse, restarted tomcat, deleted the -Xmx and -Xms in catalina.ini. IVR went live again, I runs smoothly for the first 6hours based on my assessment, then just this morning, it has the <b>same issue</b>. So I restarted it, then after around 20 to 30mins or so, it experienced the same issue again! I don't have any idea what might cause this, I used the same configuration already of our old environment (physical server) to this new server(VM SERVER). Any ideas please? Any inputs would help, I attached the logs please scroll down on the logs and you will see that there are calls then the issue came-up.

Hi All, still can't understand a thing about this issue. I have tried to just increase the memory allocation on catalina (based from the screenshot I gave). -Xsm512 and -XmX 1536. Still having same issues. I have a fail-over, but both servers have the same issue. Hope anyone can help based from their experience.

Hi, have read the link but I don't get it. I need to know how to fix it on the server itself. hoping for more replies on this issue. I want to maximize the 8GB Ram of the server and dedicate half of it for java heap or memory size of tomcat

Hi All, I have an issue right now on my production environment. When my IVR receives plenty of calls consecutively. Tomcat is shutting down by itself, saying that it is out of memory. MY Application server is running of virtual environment with 8GB RAM Each. Please I need help to utilize it. I cannot find the tomcat 7 manager on its path.
See images of my temporary fix but it is not sufficient enough.

Hi All, I have this issue: Tomcat 7.0 is up and running on the application server, callflow we're loaded on the tomcat manager, but the callflow is not responding when being verified on the EPMS. I have two servers, .32 and .33. Lets say I verify the callflow on .32 o the EPMS, it is working but the .33 callflow is not working when verified on EPMS. Both servers had the same configuration. What am I missing on this?

Hi All, I can successfully assign the VDN Number to the variable named "VDN", please see attached image. I'm not sure what's the issue here, I think on the csr transfer node, it cannot really see the vdn number or the variable itself.