Dear All,

We have migrated (upgraded) an existing OD application 6.0 to 7.1.

Steps performed as part of the up gradation
1) Downloaded the 7.1 OD
2) Installed and Completed the required configuration to run OD 7.1
3) Imported the existing OD application 6.0 while importing i was prompted whether i would like to update the runtime as they are outdated. I continued the up gradation.
4) Post up gradation there were few build path issues, after fixing them i was able to export the application to war file i was able to do all the validation on validation JSP pages
5) Exported the runtime libraries and added the server libraries on Tomcat server.

Issue encountered:
While testing this upgraded application , call gets disconnected abruptly while loading any random new items like menu, subflow in the flow files.

Troubleshooting done:

In logs and browser logs we are found the following errors

PAVB_00191
HTTP Error for url = http://URL/TopMenu-InitRepCount1?___DDSESSIONID=7B84DAB3DE80548E90DE0E62215E7580%3A%APPNAME, Method = POST, HttpStatus = 500, HTTPStatusDescription = Internal server error

@2017-01-09 04:29:31,393|PAVB_03001|ERROR|VB|5798|Session=IIHOCCMPP01-2017009122925-1|Unable to load VoiceXML DTD. XML parsing error from DOM. System Id: http://URL/AvayaSessionTerminationServlet?___DDSESSIONID=1FC976C71E852262FE877F790FAB7CDB%3A%2FAPP_NAME in Line 1, at Column 1, Exception Message: Invalid document structure, File Content: |URL####


When i deploy a new application i don't see this error.

1) I believe when VoiceBrowser is requesting for next VXML , web server is returning HTML 500 error code to which Voicebrowser is throwing PAVB_03001, Am i right
2) If my above understanding is right, i need to optimize Tomcat server settings?

Please share your thoughts

Subin.

Error 500 generally means there is a sever error on the application server. Is there anything in the catalina.out, or trace.log? you shoudl enable all tracing on the app and repeat the test and post the resulting log. Also check the report.log or the application report on the EPM.

Found this exception in trace

10/01/2017 19:48:18:913 ERROR - 60DF6F009608EEBE35DB9EA0FD2C9778:/APP_NAME :
java.lang.NullPointerException
at com.avaya.sce.runtime.SCEServlet.reportUtteranceIfOne(SCEServlet.java:420)
at com.avaya.sce.runtime.SCEServlet.processRequest(SCEServlet.java:653)
at com.avaya.sce.runtime.AppServlet.processRequest(AppServlet.java:76)
at com.avaya.sce.runtime.SCEServlet.requestHandler(SCEServlet.java:243)
at com.avaya.sce.runtime.SCEServlet.doPost(SCEServlet.java:148)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:643)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:723)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:861)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:612)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:503)
at java.lang.Thread.run(Unknown Source)

What is happening is that the runtime is looking for ___utterance in the request parameters. If it see a request parameter that ends in that, we assume it is from an input node and try to store that into an OD variable.

Is it possible to get a trace.log too?

Generally this indicates a possible problem in the upgrade of your application. Does it also happen in simulation?

Thanks for your interest.

1) This exception trace is from trace.log only.
2) This happens in simulation as well

If this indicates problem in the upgrade. Please provide document detailing upgrade steps, best practices and other details. I will upgrade one more time after going through it.

Would you mind email me a copy of the app to yakulis@avaya.com and letting m e know the steps to reproduce?

Hi Ross,

1) I am sorry, due to compliance and policies i can't the share the source code.
2) One observation though, I deployed the OD 6.0 application directly on AEP 7.1 without upgrading the runtime to OD 7.1. Found no issues while testing it.
3) Will try to upgrade the runtime to OD 7.0 instead and OD 7.1 and see the outcome.

So my question,

If we go ahead without upgrading the OD 6.0 runtime to 7.1 would it okay? I know its not a best practice, currently our application doesn't use any features of OD 7.1, so i don't any risk why we can't go ahead with OD6.0 without upgrading the runtime to OD 7.1

Please share your thoughts

Thanks,
Subin.

As a general rule we only support 2 releases backward compatibility with API so for 7.1 that would be 7.0 and 7.01. However as you noticed 6.0 happened to work. If you had a support issue, the first thing you would be asked to do is upgrade.


Can you at least post or email directly to me the trace.log? If not I cannot help you out.