Hi,

I have a trouble after taking the procecure.
How can I solve the problem?

I have the following system.
Websphere 9 / Java 8 / OD 8.1.2

There is section (Page 429) of "Performing additional WebSphere configuration" in Avaya Orchestration Designer Developer's Guide.
I followed the procedure of Performing additional WebSphere configuration.

After taking the procedure, the call flow does not work fine.

This is call flow log.
The call flow stopped that it was trying to get the parameters from VPMS.

27/06/2023 15:24:53:114 INFO - NvauIBPcNnFwoUJZcMgvQr1:/Loopflow : HTTP Session lost removing SCESession NvauIBPcNnFwoUJZcMgvQr1
27/06/2023 15:24:53:114 INFO - NvauIBPcNnFwoUJZcMgvQr1:/Loopflow : SCESession Removed
27/06/2023 15:24:53:114 DEBUG - NvauIBPcNnFwoUJZcMgvQr1:/Loopflow : Removing 0 session stack frames.
27/06/2023 15:29:22:583 INFO - uXqZOzSI8Tlu_rIAAWMr6-o:/Loopflow : SCESession bound to HttpSession uXqZOzSI8Tlu_rIAAWMr6-o
27/06/2023 15:29:25:724 INFO - uXqZOzSI8Tlu_rIAAWMr6-o:/Loopflow : Browser Version 2.1.4, terminationURL enabled : true
27/06/2023 15:29:25:724 DEBUG - uXqZOzSI8Tlu_rIAAWMr6-o:/Loopflow : PlatformParams:getPlatformParams: __VPVarGlobalDate is 1684908384864
27/06/2023 15:29:25:724 DEBUG - uXqZOzSI8Tlu_rIAAWMr6-o:/Loopflow : PlatformParams:getPlatformParams:Timestamp is 05/24/23 15:06:24
27/06/2023 15:29:25:724 DEBUG - uXqZOzSI8Tlu_rIAAWMr6-o:/Loopflow : PlatformParams: get global parameters from VPMS...

Regards,
Kodera

This is additional information.

OD call flow put error log to report.log.

[23/06/28 12:46:41:630 JST] 00000200 ServletWrappe E com.ibm.ws.webcontainer.servlet.ServletWrapper service Uncaught service() exception thrown by servlet Start: java.lang.NoSuchMethodError: org/apache/neethi/Constants.isPolicyElement(Ljavax/xml/namespace/QName;)Z (loaded from file:/C:/Program Files/IBM/WebSphere/AppServer/plugins/org.apache.axis2.jar by org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader@ded4d618[org.apache.axis2:7.0.0(id=287)]) called from class org.apache.axis2.util.PolicyUtil (loaded from file:/C:/Program%20Files/IBM/WebSphere/AppServer/lib/ext/axis2-kernel-1.8.0.jar by
com.ibm.ws.classloader.ExtJarClassLoader@ecb0d207[server:0]
Local ClassPath: C:\Program Files\IBM\WebSphere\AppServer\lib\ext\axiom-api-1.3.0.jar;C:\Program Files\IBM\WebSphere\AppServer\lib\ext\axiom-dom-1.3.0.jar;C:\Program Files\IBM\WebSphere\AppServer\lib\ext\axiom-impl-1.3.0.jar;C:\Program Files\IBM\WebSphere\AppServer\lib\ext\axis2-adb-1.8.0.jar;C:\Program Files\IBM\WebSphere\AppServer\lib\ext\axis2-adb-codegen-1.8.0.jar;C:\Program Files\IBM\WebSphere\AppServer\lib\ext\axis2-codegen-1.8.0.jar;C:\Program Files\IBM\WebSphere\AppServer\lib\ext\axis2-jaxws-1.8.0.jar;C:\Program Files\IBM\WebSphere\AppServer\lib\ext\axis2-json-1.8.0.jar;C:\Program Files\IBM\WebSphere\AppServer\lib\ext\axis2-kernel-1.8.0.jar;C:\Program Files\IBM\WebSphere\AppServer\lib\ext\axis2-saaj-1.8.0.jar;C:\Program Files\IBM\WebSphere\AppServer\lib\ext\axis2-transport-http-1.8.0.jar;C:\Program Files\IBM\WebSphere\AppServer\lib\ext\axis2-transport-local-1.8.0.jar;C:\Program Files\IBM\WebSphere\AppServer\lib\ext\VPAppLogClientWS_8.1.2.jar;C:\Program Files\IBM\WebSphere\AppServer\lib\ext\VPWebServiceClient-08.12.11.01.jar;C:\Program Files\IBM\WebSphere\AppServer\lib\ext\commons-codec-1.15.jar;C:\Program Files\IBM\WebSphere\AppServer\lib\ext\commons-httpclient-3.1.jar;C:\Program Files\IBM\WebSphere\AppServer\lib\ext\commons-logging-1.2.jar
Parent: com.ibm.ws.classloader.ProtectionClassLoader@cf013547
Delegation Mode: PARENT_LAST).
at org.apache.axis2.util.PolicyUtil.getPolicyChildren(PolicyUtil.java:289)
at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:157)
at org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:628)
at org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigurator.java:116)
at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:210)
at org.apache.axis2.client.ServiceClient.configureServiceClient(ServiceClient.java:151)
at org.apache.axis2.client.ServiceClient.<init>(ServiceClient.java:143)
at com.avaya.xml.ws.vpappvars.voiceportal.VPAppVarsServiceStub.<init>(VPAppVarsServiceStub.java:95)
at com.avaya.xml.ws.vpappvars.voiceportal.VPAppVarsServiceStub.<init>(VPAppVarsServiceStub.java:81)
at com.avaya.xml.ws.vpappvars.voiceportal.VPAppVarsServiceStub.<init>(VPAppVarsServiceStub.java:130)
at com.avaya.vp.ws.EPMWebServicesClientBaseImpl.getAppVarsAxis2(EPMWebServicesClientBaseImpl.java:595)
at com.avaya.vp.appruntimevars.VPAppRuntimeVars.getAppRuntimeVarsFromVPMS(VPAppRuntimeVars.java:318)
at com.avaya.vp.appruntimevars.VPAppRuntimeVars.getAppRuntimeVars(VPAppRuntimeVars.java:109)
at com.avaya.vp.appruntimevars.VPAppRuntimeVars.getGlobalAppRuntimeVars(VPAppRuntimeVars.java:132)
at com.avaya.runtimecommon.platforms.vp.PlatformParams.checkForUpdate(PlatformParams.java:71)
at com.avaya.sce.runtimecommon.SCESession.getSession(SCESession.java:780)
at com.avaya.sce.runtimecommon.SCESession.getSession(SCESession.java:318)
at com.avaya.sce.runtime.SCEServlet.requestHandler(SCEServlet.java:163)
at com.avaya.sce.runtime.SCEServlet.doGet(SCEServlet.java:140)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
at com.avaya.sce.runtime.Entry.service(Entry.java:52)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1235)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:779)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:179)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:143)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:96)
at org.apache.logging.log4j.web.Log4jServletFilter.doFilter(Log4jServletFilter.java:71)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:197)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:90)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:979)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1119)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:82)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:963)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1817)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:382)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:465)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:532)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:318)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:289)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1909)

Hi.


The most common reasons of the error message

"java.lang.NoSuchMethodError: org/apache/neethi/Constants.isPolicyElement"

are

- your Apache Neethi version is low (Neethi is used by Axis2 and REST for Web service connectivity)

- your project is using/imported multiple neethi.jar (Ex. two) and they are conflicting


Another not so common reason (honestly I never found this case): your neethi.jar is conflicting with axis2.jar



What release of the neethi.jar are you using ?

Please check your current Neethi (if I remind fine, 3.0.2 should be present as default in the runtime files) then add the latest/a newer version into the classpath/runtime files.

You can find the method 'org.apache.neethi.Constants.isPolicyElement()' from neethi-3.0.1.jar onwards.

Make sure just one Neethi is present in the classpath/runtime files.

HI,

I installed neethi-3.1.1.jar on ${WAS_INSTALL_ROOT}/lib/ext/ directory.
neethi-3.1.1.jar is provided by Avaya in runtimeSupportWebSphere.zip.

I confirmed the application validation screen.
The application uses org.apache.axis2.jar instead of neethi-3.1.1.jar.

Found Apache-Axis2 (org.apache.neethi.Policy)
at C:\Program Files\IBM\WebSphere\AppServer\plugins\org.apache.axis2.jar
Version of jar file may not be correct expected neethi-3.0.2.jar

Regards,
Kodera

Hi.

The message says 'expected 3.0.2'

Anyway Neethi 3.1.1 > 3.0.2 . Please test now if everything works fine and the error message is still present/no longer present. Otherwise try the release 3.0.2.

Hi,

Thank you for your support.
It works fine.

I tried to add "${WAS_INSTALL_ROOT}/lib/ext/neethi-3.1.1.jar" to shared file.
After adding the file, the application validation screen was changed from org.apache.axis2.jar to neethi-3.1.1.jar.

Found Apache-Axis2 (org.apache.neethi.Policy)
at C:\Program%20Files\IBM\WebSphere\AppServer\lib\ext\neethi-3.1.1.jar
Version of jar file may not be correct expected neethi-3.0.2.jar

And then I tested to call the flow, it works fine without problem.

Thanks your advice.

Regards,
Kodera

Hi Kodera.

If now the call flow works fine without the original error message, it means the release 3.1.1 was successfully accepted.

Hi massimo,

Thank you for confirmation.

I will share the information to my colleagues.

Regards,
Kodera