Hello. Ross Yakulis assisted me with created a PDC to use for an application. After deploying that application which uses CAVs, it appears that there is an issue with the app contacting the EPM and pulling down the CAV information. Please see below from VPAppLogClient.log. I did confirm connectivity by browsing to https://165.137.158.90/axis2/services/VPAppVarsService from the app server and am challenged with username/password--

2017-04-21 09:50:44,197 67800890 [catalina-exec-6] ERROR  - VPAppRuntimeVars:getAppRuntimeVarsFromVPMS(): No callable EPM to get Application Runtime Vars

2017-04-21 09:50:44,197 67800890 [catalina-exec-6] ERROR  - VPAppRuntimeVars:printRuntimeVars: response received is NULL

2017-04-21 09:50:55,009 67811702 [VPAppRuntimeVarsMonitorThread: https://165.137.158.90/axis2/services/VPAppVarsService] ERROR  - VPAppRuntimeVars:EPMWebServicesClientBaseImpl:getAppVarsAxis2() Caught Exception FAILED to send request to https://165.137.158.90/axis2/services/VPAppVarsService Application Name:  From AE Server: NCOAPP-PO-P01 with error: null NOTE: It could be caused by this EPM is not online or some other network issues.

java.lang.ClassCastException

2017-04-21 09:50:55,009 67811702 [VPAppRuntimeVarsMonitorThread: https://165.137.158.90/axis2/services/VPAppVarsService] ERROR  - VPAppRuntimeVars:EPMWebServicesClientBaseImpl:getAppVarsAxis2() sent failed, add to monitor list: https://165.137.158.90/axis2/services/VPAppVarsService

2017-04-21 09:50:55,009 67811702 [VPAppRuntimeVarsMonitorThread: https://165.137.158.90/axis2/services/VPAppVarsService] ERROR  - AppRuntimeVarsMonitor:callAppRuntimeVarsWS: VPAppRuntimeVarsMonitorThread: https://165.137.158.90/axis2/services/VPAppVarsService Failed to get App Runtime Vars

Can you post the app's trace.log file and the vpapplogclient.log file instead of pasting only some of the content? What app server are you on?

Sure no problem. We are on Tomcat 7 Windows Server 2012.

I turned on debug mode for vpappclient restarted and it was working. Seeing that it was working and thinking the reboot did the trick, I turned log level back to WARN, and restarted tomcat again. According to the log, it only worked for a little while. It is now back to not working.

I've attached a new log that has the DEBUG information included. The actual app that we have variables enabled for is "ConsentIVR" and the two variables are seqAPIKey and seqHostname if that helps you search.

I am contacting the expert in this area. So you may have wait a little bit before I can get back to you.

I appreciate it Wilson, continuing to troubleshoot our end as well.

What exactly did you reboot to make it work for a little bit? Have you tried restarting EPM?

We have not restarted EPM. I restarted the application server (when I enabled DEBUG for vpapplog).

Could you send the file list in the Tomcat's lib directory? We are suspecting there are some conflicting files.

Also what version is your EPM?

Two EPMs, both 7.0.2. File server list attached for both servers.

It seem the 2 separate lists each from 2 different app servers. Do you mean the app server is on the EPM machine, and both of the app server have the same problem? We don't see any problem with the files listed but the error is still pointing to conflicting Axis2 library. Do you happen to have axis or axis2 library files in the app's lib directory?

No there are two EPM Servers. There are also 2 application servers running tomcat on Windows Server 2012.

There are no axis 2 files in this application's WEB-INF. However, there are other apps on the application server that we do in fact have a later version of axis2 in their lib directory due to issues with the OD provided version of axis2.

 Directory of D:\apache-tomcat-7.0.69\webapps\ConsentIVR\WEB-INF\lib



04/21/2017  10:15 AM    <DIR>          .

04/21/2017  10:15 AM    <DIR>          ..

04/21/2017  11:11 AM            28,798 adminvar-rt-07.10.12.02.jar

04/21/2017  11:11 AM            37,513 avrest-rt-07.10.12.02.jar

04/21/2017  11:11 AM            10,441 ccSerilogJ-00.00.07.jar

04/21/2017  11:11 AM            91,744 ConsentIVR.jar

04/21/2017  11:11 AM           487,415 scert-07.10.12.02.p2.jar

               5 File(s)        655,911 bytes

               2 Dir(s)  68,716,883,968 bytes free



D:\apache-tomcat-7.0.69\webapps\ConsentIVR\WEB-INF\lib>

The axis2 files in the other apps should not be necessary since the same files are accessible at the system level. I suspect that is the problem. You may need to set up another Tomcat (for testing) with only the apps without the axis2 files and try to see if the problem persists.

If that is the case, how do I reconcile the fact that some apps REQUIRE a newer version of axis2? I was told here that it was no issue to put a later version of axis2 in an app's WEB-INF/lib directory so that it would load those files instead of from tomcat/lib.