Hi,
We are having this same issue with OD 7.2.1
The spring classes inside the activemq-all-5.13.1 jar are making conflicts with spring framework libraries.
After deleting the jar the conflicts disappeared, but we want to confirm is that is the recommended procedure.

Thanks,
Alfredo

Ok. Thank you for the quick answer.

Hi,
We are having an issue with the conditions and expressions in OD 07.10.12.02.
I've performed several tests and the results indicate that it could be a framework issue.

The scenario is the following:
Create a simple Speech module with 2 Project Variables and one Data node:

Initialize the Project variables with boolean values:

var1 = true
var2 = false

Then in a Data node evaluate the conditions as follows:

If var1 is true AND if var2 is true GoTo path1
ELSE GoTo path2

This tests should go to path2 but is going to path1 instead.

Please find attached the full trace log and the module code.

Thanks,
Alfredo

Yes, that is what is happening, I've added new CAVs to an existing app alrady definded on EPMS.

I've defined a new app on EPMS and the list is updated.

This is a production environment so I can't define a new application after a new CAV is added.

I think the issue is happening on applications configured as Load Balance with 2 URIs.
I've fix the issue as a workaround setting the application as "Single URI" and the CAVs were refreshed
Then I ve set back to the load balance setting and it's working fine.

Environment:
OD Scert 07.00.18.01
Experience Portal 7.0.0.0.6605
Apache Tomcat 6.0.24


I've added new cavs to the main application module and after making the deployment on the environment (Tomcat) the EP does not update the cav list on Application Configuration.

The source code deployed has correctly the variables on IProjectVariables.class

I've also validated the adminvarinfo.xml file from the module deployed and the new cavs are also there.


But the EP is not showing the new fields and also the application log shows that the new cavs are not being loaded.

The new cavs are:
dropOffUK
dropOffAT
dropOffBE
dropOffCH
dropOffDE
dropOffES
dropOffFR
dropOffIE
dropOffIT
dropOffNL
dropOffPL

On the attached zip file you can find:

The war file and the folder deployed (OD_Driver.war).
The UPS.log file is the OD trace log.
The catalina.out log from tomcat with deployment info.

Thanks,
Alfredo.

It works. Thanks.

Hi Ross,
It seems like this patch partially fixes the bug. It fixes the left variable but it still an issue with the right variable.

Thanks,
Alfredo

Thanks,
I'm sending the logs by email.
We have 190 extensions. We just made 60 simultaneus calls and we got 4 calls with the delay.

The calls to look at are:

Failed call on port 87291, duration 81 seconds, start time 10:26:54
Failed call on port 87312, duration 67 seconds, start time 10:27:47
Failed call on port 87342, duration 67 seconds, start time 10:27:06
Failed call on port 87374, duration 67 seconds, start time 10:26:47

Sample good call:
port 87364, duration 57 seconds, start time 10:28:14

Thanks,
Alfredo

Hi,
I'm having an issue with an application using aesconnector (OD 06.00.13.01). For some calls it's taking 10 to 20 seconds to complete the transfer.
We've disabled all logging and also set some parameters into TSAPI.pro file as recomended (maxThreadPoolSize=100; tsDevicePerformanceOptimization=true).
We can reproduce this behavior at will, making 30 simultaneous calls we'll get 4 calls with this delay.

If there somthing we can check or some logs you can review please let me know.

Thanks,
Alfredo

Thanks Ross, log file sent by email.

Hi,
We are having a critical issue in a customer environment using Oracle WebLogic, EPM 6.0.2.0.0501 and OD 06.00.10.02.p1.

The exception appears randomly in any time and any node in the callflow. We can call the same application with the same scenario and this exception could appear or not and never happens in the same place. We have been monitoring and collecting application logs and we have concluded that its not an application issue. It should be something wrong into OD servlets handler or an incompatibility with WebLogic.

I've reviewed other threads in this forum but there aren't solutions for this issue.

[APP]|[03 Sep 2013 12:56:35,840]|[ INFO]|[MESSAGE: ZtTwSmJV0By2TvQznlrFQRwm1Nmyc5ndN3pcLhZ6KR5VchSWDV5t!1046382273!1378227317958:/PAYX_ProductMenu : Capturing exception [java.lang.IllegalStateException]. Message [Cannot forward a response that is already committed]]
[APP]|[03 Sep 2013 12:56:35,854]|[ERROR]|[MESSAGE: ZtTwSmJV0By2TvQznlrFQRwm1Nmyc5ndN3pcLhZ6KR5VchSWDV5t!1046382273!1378227317958:/PAYX_ProductMenu : session id:vpsmpp01-2013246165517-6 | Error processing request
EXCEPTION>
java.lang.Exception: java.lang.IllegalStateException: Cannot forward a response that is already committed
   at com.avaya.sce.runtime.AppServlet.processRequest(AppServlet.java:130)
   at com.avaya.sce.runtime.SCEServlet.requestHandler(SCEServlet.java:282)
   at com.avaya.sce.runtime.SCEServlet.doGet(SCEServlet.java:181)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
   at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
   at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
   at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
   at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:183)
   at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:529)
   at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:253)
   at com.avaya.sce.runtime.SCEServlet.forward(SCEServlet.java:1303)
   at com.avaya.sce.runtime.Entry.handleRequest(Entry.java:290)
   at com.avaya.sce.runtime.AppDocument.processRequest(AppDocument.java:241)
   at com.avaya.sce.runtime.SCEServlet.requestHandler(SCEServlet.java:282)
   at com.avaya.sce.runtime.SCEServlet.doGet(SCEServlet.java:181)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
   at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
   at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
   at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
   at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:183)
   at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3686)
   at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
   at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
   at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
   at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
   at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
   at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
   at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
   at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.IllegalStateException: Cannot forward a response that is already committed
   at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:122)
   at com.avaya.sce.runtime.SCEServlet.forward(SCEServlet.java:1303)
   at com.avaya.sce.runtime.BasicServlet.handleRequest(BasicServlet.java:116)
   at com.avaya.sce.runtime.AppServlet.processRequest(AppServlet.java:96)
   at com.avaya.sce.runtime.SCEServlet.requestHandler(SCEServlet.java:282)
   at com.avaya.sce.runtime.SCEServlet.doGet(SCEServlet.java:182)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
   at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
   at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
   at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
   at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:184)
   at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:529)
   at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:253)
   at com.avaya.sce.runtime.SCEServlet.forward(SCEServlet.java:1304)
   at com.avaya.sce.runtime.Entry.handleRequest(Entry.java:290)
   at com.avaya.sce.runtime.AppDocument.processRequest(AppDocument.java:241)
   at com.avaya.sce.runtime.SCEServlet.requestHandler(SCEServlet.java:282)
   at com.avaya.sce.runtime.SCEServlet.doGet(SCEServlet.java:182)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
   at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
   at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
   at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
   at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:184)
   ... 9 more

Hi,

We have an application already in production that was developed with DD 5.1.0.1503 and it's deployed on Apache Tomcat/6.0.32.
We are currently experiencing permGem OutOfMemoryErrors and I've found that when I startup or shutdown Tomcat it's generating the following errors:

SEVERE: The web application [/CF_Main] appears to have started a thread named [VPBatchLogWriterThread: https://10.65.192.83/axis2/services/VPAppLogService] but has failed to stop it. This is very likely to create a memory leak.
Jul 26, 2012 5:28:11 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/CF_Main] appears to have started a thread named [LicenseTimer-Refresh] but has failed to stop it. This is very likely to create a memory leak.

I've check for old threads on this forum but I couldn't find much information regarding this error.
If you have any information please let me know.

Thanks,
Alfredo

I want to know if there's any way to dynamically modify the max length property value of a record item. This value is hardcoded on the properties of the record item and I need to have this value in a variable.

I'm using a Record item and I'm having problems with max length property. I set it for 180 seconds and it's always finishing when it reaches 120 seconds (2 minutes). I changed it several times with different length size and always ends in 2 minutes maximum.

I'm using Voice Portal 3 to test it. Could it be a platform restriction? Didn't find anything related on VP documentation.

Thanks,
Alfredo

Hi,

Using OD6 with SP3 on an EP6.0

I'm working on an environment failover tests and I've found that when the EPM is down the application takes 5 seconds to fetch the CAVs and continue with the app flow.

Is there any parameter that we can use to reduce this timeout?

Following is a piece of call log example where I see that delay.

[APP]|[13 Nov 2013 13:41:17,177]|[DEBUG]|[MESSAGE: nTHLSDHNZhpQ64pZFmbHyLPvX5MGdfkc2MK8DLGg1CGYNzZJhPYf!1964709017!1384368077164:/PAYX_ProductMenu : AdminVarCache:init: load data from the Voice Portal/Experience Portal platform]
[APP]|[13 Nov 2013 13:41:23,204]|[ERROR]|[MESSAGE: nTHLSDHNZhpQ64pZFmbHyLPvX5MGdfkc2MK8DLGg1CGYNzZJhPYf!1964709017!1384368077164:/PAYX_ProductMenu : VPClientProxy:VPAppRuntimeVars.getAppRuntimeVars returns null]
[APP]|[13 Nov 2013 13:41:23,204]|[DEBUG]|[MESSAGE: nTHLSDHNZhpQ64pZFmbHyLPvX5MGdfkc2MK8DLGg1CGYNzZJhPYf!1964709017!1384368077164:/PAYX_ProductMenu : AdminVarCache:init: no data comes back from proxy.]


Thanks,
Alfredo