Please login or register to access secure site features.

Note: By continuing to use DevConnect Program Services you agree to our latest Registered Member Terms.

Sign in using DevConnect ID

Forgot password?

Trouble logging in?

Submit a ticket for Registration Support.

I have an SSO ID

?
sign in

Don't have a DevConnect or SSO ID ?

Create a DevConnect account or join the program.

register now
^
Messages posted by: Smpphillips
Forum Index » Profile for Smpphillips » Messages posted by Smpphillips
Message
In this case I deleted the project and reimported again, and didn't run into the same issue and I no longer have a copy of what the project tree looked like. Unfortunately I'm not sure what specifically went wrong on the first attempt.
When I right click on my main.flow file in Avaya OD Navigator, and select Orchestration Designer > Generate

I get the error message "Callflow code generator invoked on non-flow project."

The project is definitely a speech project, so why does OD not recognise it as one? What causes the error message to show? Is there a particular file missing?
I've worked this out. A process outside of AAOD on my computer had (accidentally) amended some files, causing Eclipse to not recognise the project properly. Presumably as a result of this, it was unable to verify the project version, so assumed it was out-of-date and it then tried to update it.

I closed and deleted the project from Eclipse, got a clean copy and reimported.

When I reopened Eclipse, it again prompted me to update, stating the imported project was out-of-date. This time it completed with no errors and builds seem to be working fine now.

Thanks
When I open AAOD, I get a dialog named "Upgrade Project" stating, "Project upgrade is about to run on workspace <full qualified name>, this is a non-reversible operation. Do you want to continue?"

If I click yes, I get an error with the following exception in the error log.

Error: eclipse.buildId=4.8.0.I20180124-2000
java.version=1.8.0_251
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_GB
Command-line arguments: -os win32 -ws win32 -arch x86_64

com.avaya.sce.core
Error
Thu Mar 04 14:38:45 GMT 2021
Caught exception upgrading project. Project "<project name>" update class: com.avaya.sce.callflow.internal.CallflowProjectUpdater

java.lang.ArithmeticException: / by zero
at com.avaya.sce.callflow.internal.CallflowProjectUpdater.updateCallflow_VERSION_05_25_07(CallflowProjectUpdater.java:553)
at com.avaya.sce.callflow.internal.CallflowProjectUpdater.upgradingProject(CallflowProjectUpdater.java:179)
at com.avaya.sce.core.internal.ProjectVersionUpgradeMgr$ProjectVersionUpgradeOperation$1.visit(ProjectVersionUpgradeMgr.java:215)
at com.avaya.sce.core.internal.ProjectVersionUpgradeMgr$ProjectVersionUpgradeOperation$1.visit(ProjectVersionUpgradeMgr.java:1)
at com.avaya.ade.common.core.utils.eclipse.Extensions.loadExtensionFromPluginRegistry(Extensions.java:50)
at com.avaya.sce.core.internal.ProjectVersionUpgradeMgr$ProjectVersionUpgradeOperation.updateProject(ProjectVersionUpgradeMgr.java:232)
at com.avaya.sce.core.internal.ProjectVersionUpgradeMgr$ProjectVersionUpgradeOperation.execute(ProjectVersionUpgradeMgr.java:181)
at org.eclipse.ui.actions.WorkspaceModifyOperation.lambda$0(WorkspaceModifyOperation.java:107)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2214)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:128)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:437)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:353)
at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:483)
at com.avaya.sce.core.internal.ProjectVersionUpgradeMgr.projectIDEUpdateCheck(ProjectVersionUpgradeMgr.java:110)
at com.avaya.sce.core.CorePlugin$1.run(CorePlugin.java:163)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:37)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4218)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3825)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:681)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:595)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:152)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:656)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:592)
at org.eclipse.equinox.launcher.Main.run(Main.java:1498)


I have several questions:
Why do I need to upgrade project in the first place?
Why does the arithmetic exception occur (I don't have the code for this to look into it)?
I noticed a versioned method is called (updateCallflow_VERSION_05_25_07) is this the problem?
How do I stop seeing this error?

Thanks in advance.
Agreed, I don't think I've done this before. Is there a guide to how to do this?
From testing the scenario, I get these logs out even if the call doesn't end whilst in that sub-module. For example I get the logs out even for a call that continues for a few more minutes after entering and exiting the sub-module.

Do you know if there's any other instance that this error might occur?
Request is invalid sessionid [<redacted1>:/IVR] class [flow.Start] and saved class name [flow.<dialog1> is -> false
Request is invalid sessionid [<redacted1>:/IVR] class [flow.Start] and saved class name [flow.<dialog1> is -> false
Request is invalid sessionid [<redacted2>:/IVR] class [flow.Start] and saved class name [flow.<dialog2> is -> false
Request is invalid sessionid [<redacted2>:/IVR] class [flow.Start] and saved class name [flow.<dialog2> is -> false
Request is invalid sessionid [<redacted3>:/IVR] class [flow.Start] and saved class name [flow.<dialog1> is -> false
Request is invalid sessionid [<redacted3>:/IVR] class [flow.Start] and saved class name [flow.<dialog1> is -> false
Request is invalid sessionid [<redacted3>:/IVR] class [flow.Start] and saved class name [flow.<dialog1> is -> false
Request is invalid sessionid [<redacted3>:/IVR] class [flow.Start] and saved class name [flow.<dialog1> is -> false
Request is invalid sessionid [<redacted4>:/IVR] class [flow.Start] and saved class name [flow.<dialog3> is -> false
Request is invalid sessionid [<redacted4>:/IVR] class [flow.Start] and saved class name [flow.<dialog3> is -> false

Unfortunately there are no further related logs or datetime stamps.

The lines of logging always appear 2 at a time and from testing, both lines are generated on the first pass through the dialog.
I've got an issue where we're seeing the below line of logging repeatedly:

Request is invalid session id [<sessionid>:<source>] class <start of flow> and saved class name [<class name> is -> false

I've established that the log seems to occur whenever I go to 3 specific dialogs. Interestingly when I do, the dialogs play fine, they take input fine and they progress the call fine - it seems there's no issue to the user, the only issue seems to be that we're getting logs!

I've searched previous posts in the forum but haven't found a situation that matches what we are seeing. It isn't the case that the user has hung up, as I have replicated the issue without needing to hang up.

Has anyone seen this before and worked out the cause? Any advice would be appreciated.
 
Forum Index » Profile for Smpphillips » Messages posted by Smpphillips
Go to: