Hello,

I have simple OD application that takes the input from other application. After taking the input it process the data and return the value.
When I am calling this OD application using the F5 load balancer my application giving me error and call is going to the Bedfetch event node (I am catching error.bedfetch event in APPRoot node).
I am Getting the below error when checking the logs on log viewer tab of AEP:

error.badfetch.http.500 URI: AppName?___DDSESSIONID=fefefefef%3A%AppName
HTTP Error for url = "F5 Url"/AppName?___DDSESSIONID=fefefefef%3A%AppName, Method = POST, HttpStatus = 500, HTTPStatusDescription = Internal server error

If I call application without F5, it is working fine.

Can somebody help me on the above issue.


Thanks in advance.

Hello Support Team,

Can somebody help me on above problem.

Thanks.

Hi.

a) "If I call application without F5, it is working fine."

I suppose the issue is caused by the F5 Load Balancer, maybe a setting there.



b) 'ERROR|Cache|HTTP Error for url ...- HttpStatus = 500, HTTPStatusDescription = Internal server error' and '|ERROR|Interpreter|error.badfetch.http.500'
are generic error messages usually related to an unhandled exception (null pointer or other error).

- Try cleaning/regenerating the project (when you are in the speech perspective, right click on project -> Orchestration Designer -> Generate Project) and restarting the app server. Sometimes this helps.

- If that doesn't fix it, then check if there are any stack traces in the application server log to indicate what happened (the exact exception's message).


For your reference, here an example from a different case (IT IS JUST AS EXAMPLE FROM A DIFFERENT DEVCONNECT MEMBER): 'HTTP Status 500 – Internal Server Error - com.avaya.sce.runtimecommon.SCERuntimeException: Language [en-us] is invalid for this application'


To troubleshoot the issue, OD logs, the app server logs and the F5 Load Balancer logs can be the proper starting point for any clue. In case the problem is caused by the Load Balancer, check F5 docs or contact them.

Hello massimo__croci,

Thanks for the reply.
Other than above errors I am not getting any errors in the OD application logs.

The problem is When I am using the F5 then my call is going to Bedfetch event node (I am catching error.bedfetch event in APPRoot node).
Without the F5 the call is working fine.
I compared the trace.log file of the application for Good and Bad call. I can see there is some parameters from VPMS is missing. I am not sure this will be the issue.
Below are the parameters which is missing in Bad call VS Good call:

BAD CALL LOGS:

21/06/2023 05:18:12:703 INFO - fefefefef%3A%AppName : SCESession bound to HttpSession fefefefef
21/06/2023 05:18:12:703 INFO - fefefefef%3A%AppName : Browser Version 2.1.4, terminationURL enabled : true
21/06/2023 05:18:12:703 DEBUG - fefefefef%3A%AppName : PlatformParams:getPlatformParams: __VPVarGlobalDate is 1687192324161
21/06/2023 05:18:12:703 DEBUG - fefefefef%3A%AppName : PlatformParams:getPlatformParams:Timestamp is 06/19/23 12:32:04
21/06/2023 05:18:12:703 INFO - fefefefef%3A%AppName : Using SCESession fefefefef%3A%AppName servlet : Start
21/06/2023 05:18:12:705 INFO - fefefefef%3A%AppName : ** Pushed Stack Frame [/AppName]
21/06/2023 05:18:12:705 INFO - fefefefef%3A%AppName : Storing :session___sessionid to complex: session:sessionid as [2023172091f]
21/06/2023 05:18:12:706 DEBUG - fefefefef%3A%AppName : no variable for simple: __VPvpms
21/06/2023 05:18:12:707 DEBUG - fefefefef%3A%AppName : no variable for simple: __VPapptracelevel
21/06/2023 05:18:12:708 INFO - fefefefef%3A%AppName : Storing :InputDNIS to simple: InputDNIS as [123456789112]
21/06/2023 05:18:12:708 DEBUG - fefefefef%3A%AppName : *** Reply for [/AppName/Start] ***
21/06/2023 05:18:12:709 DEBUG - fefefefef%3A%AppName : 0:<?xml version="1.0" encoding="UTF-8"?>



GOOD CALL LOGS:

21/06/2023 05:19:31:856 INFO - Dbfiwebfbew:/AppName : SCESession bound to HttpSession Dbfiwebfbew
21/06/2023 05:19:31:856 INFO - Dbfiwebfbew:/AppName : Browser Version 2.1.4, terminationURL enabled : true
21/06/2023 05:19:31:856 DEBUG - Dbfiwebfbew:/AppName : PlatformParams:getPlatformParams: __VPVarGlobalDate is 1687192324161
21/06/2023 05:19:31:856 DEBUG - Dbfiwebfbew:/AppName : PlatformParams:getPlatformParams:Timestamp is 06/19/23 12:32:04
21/06/2023 05:19:31:856 DEBUG - Dbfiwebfbew:/AppName : PlatformParams: get global parameters from VPMS...
21/06/2023 05:19:31:960 DEBUG - Dbfiwebfbew:/AppName : PlatformParams: AppRuntimeVarsResponse.getGlobalAppRuntimeVars returns status - success
21/06/2023 05:19:31:960 DEBUG - Dbfiwebfbew:/AppName : PlatformParams: get parameter|value - __VP__ICR__ICRCore_Address|1.12.3.1#1##1.12.3.1#1
21/06/2023 05:19:31:960 DEBUG - Dbfiwebfbew:/AppName : PlatformParams: get parameter|value - __VPLicenseServerURL|https://1.12.3.1:8008/WebLM/LicenseServer
21/06/2023 05:19:31:960 DEBUG - Dbfiwebfbew:/AppName : PlatformParams: get parameter|value - __VPConversationServer|
21/06/2023 05:19:31:960 DEBUG - Dbfiwebfbew:/AppName : PlatformParams: get parameter|value - __VPConversationServerTimeout|60
21/06/2023 05:19:31:961 DEBUG - Dbfiwebfbew:/AppName : PlatformParams: get parameter|value - __VPConversationServerType|Internal
21/06/2023 05:19:31:961 DEBUG - Dbfiwebfbew:/AppName : PlatformParams: get parameter|value - __VPConversationType|Internal
21/06/2023 05:19:31:961 DEBUG - Dbfiwebfbew:/AppName : PlatformParams: get parameter|value - __VPEDContextStore|
21/06/2023 05:19:31:961 DEBUG - Dbfiwebfbew:/AppName : PlatformParams: get parameter|value - __VPEDPlatform|
21/06/2023 05:19:31:961 DEBUG - Dbfiwebfbew:/AppName : PlatformParams: get parameter|value - __VPEDPlatformTimeout|60
21/06/2023 05:19:31:961 DEBUG - Dbfiwebfbew:/AppName : PlatformParams: get parameter|value - __VPappintf|/axis2/services/VPAppIntfService
21/06/2023 05:19:31:961 DEBUG - Dbfiwebfbew:/AppName : PlatformParams: get parameter|value - __VPapplog|/axis2/services/VPAppLogService
21/06/2023 05:19:31:961 DEBUG - Dbfiwebfbew:/AppName : PlatformParams: get parameter|value - __VPappvars|/axis2/services/VPAppVarsService
21/06/2023 05:19:31:961 DEBUG - Dbfiwebfbew:/AppName : PlatformParams: get parameter|value - __VPepmguid|Dbfiwebfbew
21/06/2023 05:19:31:961 DEBUG - Dbfiwebfbew:/AppName : PlatformParams: get parameter|value - __VPzoneepm__0|1.12.3.1|1.12.3.2|1.12.3.3
21/06/2023 05:19:31:961 DEBUG - Dbfiwebfbew:/AppName : PlatformParams: get parameter|value - __VPzoneids|0
21/06/2023 05:19:31:961 DEBUG - Dbfiwebfbew:/AppName : PlatformParams: get parameter|value - __VPzonename__0|Default
21/06/2023 05:19:31:961 INFO - Dbfiwebfbew:/AppName : Using SCESession Dbfiwebfbew:/AppName servlet : Start
21/06/2023 05:19:31:962 INFO - Dbfiwebfbew:/AppName : ** Pushed Stack Frame [/AppName]
21/06/2023 05:19:31:963 INFO - Dbfiwebfbew:/AppName : Storing :session___sessionid to complex: session:sessionid as [2023172091f]
21/06/2023 05:19:31:963 DEBUG - Dbfiwebfbew:/AppName : no variable for simple: __VPvpms
21/06/2023 05:19:31:964 DEBUG - Dbfiwebfbew:/AppName : no variable for simple: __VPapptracelevel
21/06/2023 05:19:31:964 INFO - Dbfiwebfbew:/AppName : Storing :InputDNIS to simple: InputDNIS as [123456789112]
21/06/2023 05:19:31:965 DEBUG - Dbfiwebfbew:/AppName : *** Reply for [/AppName/Start] ***
21/06/2023 05:19:31:965 DEBUG - Dbfiwebfbew:/AppName : 0:<?xml version="1.0" encoding="UTF-8"?>


Please let me know your thaughts.


Thanks

Hi.

In the bad call log, it is not trying to get global parameters from the EPM (its old name was VPMS, the process has still that name).

It does not fail, otherwise you received:

DEBUG - Dbfiwebfbew:/AppName : PlatformParams: get global parameters from VPMS...
DEBUG - Dbfiwebfbew:/AppName : PlatformParams: AppRuntimeVarsResponse.getGlobalAppRuntimeVars returns status - failure


- Might you search for the file named 'VPAppLogClient.txt'?

It should say what is wrong in the 'get global parameters from VPMS' step.


- Are you using CAVs (Configurable Application Variable)?

Hi,

I am not using CAV variable.
Can you please tell me where I will get 'vpapplogclient.log' file.

Thanks

The general rule is:

Go to the app server's main directory and search for 'vpapplogclient', the exact location depends on the specific app server (it can be different in older and newer releases).

Attached an example of my Apache Tomcat 9 on Windows 10 (the main directory is "C:\Program Files\Apache Software Foundation\Tomcat 9.0").

Hi,

I check the file on my tomcat directory but there is no logs for the errors.
Can you please tell me is there any specific setting I need turn on for logs to create in 'vpapplogclient.log' file.

Thanks

If you cannot find the VPAppLogClient file in any Application Server's directories, you may need to enable the DEBUG level on the app server

a) open the file 'VPAppLogClient.log4j.properties' ipresent in the runtime support files

see (on page 454): https://kb.avaya.com/resources/sites/AVAYA/content/live/FAQ/101000/FAQ101327/en_US/Orchestration%20Designer%20Developer%27s%20Guide.pdf


b) search for the line "log4j.logger.com.avaya.vp.applog.client"

c) change there the debug level to DEBUG


After that, you'll see in the 'VPAppLogClient.log4j.properties' file

log4j.logger.com.avaya.vp.applog.client=DEBUG, VPAppLogClient


d) restart Tomcat for the logging to start