Author Message
BMatchok
Joined: May 26, 2016
Messages: 114
Offline
Software versions:
Avaya Aura® Experience Portal 7.1.0
Avaya Aura(r) Orchestration Designer Version: 7.1 (7.1.0.1202)
Websphere Application Servet 8.5.5.9

I configured a new AEP and app server. When I call in it is not passing the runtime variables. I get the log message:
VPClientProxy:VPAppRuntimeVars.getAppRuntimeVars returns null

When I point AEP to the working Websphere app server it works. So I am pretty sure it is in the Websphere server. I know this is not a Websphere forum but since it is working in conjunction with AEP I was wondering if any would knon what could be causing this.
RossYakulis
Joined: Nov 6, 2013
Messages: 2652
Offline
Do you have a trace.log to share? Is the runtime-platform set correctly?
BMatchok
Joined: May 26, 2016
Messages: 114
Offline
I am also getting the following error:

License server URl Error :java.net.MalformedURLException | null | null |

I am not sure if it is related and could be causing the initial issue
RossYakulis
Joined: Nov 6, 2013
Messages: 2652
Offline
trace? did you check we web.xml file?
BMatchok
Joined: May 26, 2016
Messages: 114
Offline
The trace logs are set on Debug and the web.xml file looks correct. It is the same applicaiton that is working on a different environment. I did see this in the SystemOut.log. It is probably the reason the variables are not being passed.



[9/21/16 12:26:47:709 EDT] 000000d5 SystemOut O 21/09/2016 12:26:47:709 ERROR - AlarmMonitorThread:EPMWebServicesClientBaseImpl:logAlarmsAxis2() - Caught Exception FAILED with AxisFault faultCode: null error: Received fatal alert: handshake_failure to log entry size: 2 to URL: https://10.27.247.80/axis2/services/VPAppLogService from AE server: emsa091d First SID: avappl001d-2016265145029-19 Last SID: avappl001d-2016265160621-1 NOTE: It could be caused by this EPM is not online or some other network issues.
org.apache.axis2.AxisFault: Received fatal alert: handshake_failure


This is everything in the trace logs
21/09/2016 12:04:20:911 ERROR - gQ7Q3bxqBx31ibyrHJKOzmw:/Dispatch : VPClientProxy:VPAppRuntimeVars.getAppRuntimeVars returns null
21/09/2016 12:30:59:691 ERROR - Z3Jkm3ogHkOf_k7nU9G9y2w:/Dispatch : VPClientProxy:VPAppRuntimeVars.getAppRuntimeVars returns null
21/09/2016 12:54:07:220 ERROR - RPycUJ-smtsMBgceAyVuNzW:/Dispatch : VPClientProxy:VPAppRuntimeVars.getAppRuntimeVars returns null
BMatchok
Joined: May 26, 2016
Messages: 114
Offline
I think the trace logs are not going to be written to because no data is being passed from Avaya. The trace settings all have to be configured in Avaya to indicate what needs to be written to the logs.

The log indicates that the VPClientProxy:VPAppRuntimeVars.getAppRuntimeVars returns null. The forums that I searched indicated that there was a connection issue between AEP and Websphere
BMatchok
Joined: May 26, 2016
Messages: 114
Offline
I just found a handshake exception in the log. Can this be why it is not passing parameters to Websphere:

9/22/16 11:31:48:287 EDT] 000001a8 HTTPSender I org.apache.axis2.transport.http.HTTPSender sendViaPost Unable to sendViaPost to url[https://10.27.247.80/axis2/services/VPAppVarsService]
org.apache.axis2.AxisFault: Received fatal alert: handshake_failure
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisRequestEntity.java:98)
at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:499)
at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2114)
at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1096)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:621)
at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:193)
at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:404)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:231)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:443)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:406)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
at com.avaya.xml.ws.vpappvars.voiceportal.VPAppVarsServiceStub.getAppRuntimeVars(VPAppVarsServiceStub.java:191)
at com.avaya.vp.ws.EPMWebServicesClientBaseImpl.getAppVarsAxis2(EPMWebServicesClientBaseImpl.java:591)
at com.avaya.vp.appruntimevars.AppRuntimeVarsMonitor$MonitorTask.callAppRuntimeVarsWS(AppRuntimeVarsMonitor.java:244)
at com.avaya.vp.appruntimevars.AppRuntimeVarsMonitor$MonitorTask.run(AppRuntimeVarsMonitor.java:286)
at java.lang.Thread.run(Thread.java:780)
Caused by: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
at com.ibm.jsse2.j.a(j.java:23)
at com.ibm.jsse2.j.a(j.java:21)
at com.ibm.jsse2.qc.b(qc.java:465)
at com.ibm.jsse2.qc.a(qc.java:451)
at com.ibm.jsse2.qc.h(qc.java:759)
at com.ibm.jsse2.qc.a(qc.java:93)
at com.ibm.jsse2.h.write(h.java:34)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:93)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:151)
at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisRequestEntity.java:94)
... 20 more

[9/22/16 11:31:48:287 EDT] 000001a8 SystemOut O 22/09/2016 11:31:48:287 ERROR - VPAppRuntimeVars:EPMWebServicesClientBaseImpl:getAppVarsAxis2() - Caught Exception FAILED with AxisFault faultCode: null error: Received fatal alert: handshake_failure send to vpms url: https://10.27.247.80/axis2/services/VPAppVarsService Application Name: From AE Server: PNOA310D NOTE: It could be caused by this EPM is not online or some other network issues.
org.apache.axis2.AxisFault: Received fatal alert: handshake_failure
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisRequestEntity.java:98)
at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:499)
at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2114)
at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1096)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:621)
at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:193)
at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:404)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:231)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:443)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:406)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
at com.avaya.xml.ws.vpappvars.voiceportal.VPAppVarsServiceStub.getAppRuntimeVars(VPAppVarsServiceStub.java:191)
at com.avaya.vp.ws.EPMWebServicesClientBaseImpl.getAppVarsAxis2(EPMWebServicesClientBaseImpl.java:591)
at com.avaya.vp.appruntimevars.AppRuntimeVarsMonitor$MonitorTask.callAppRuntimeVarsWS(AppRuntimeVarsMonitor.java:244)
at com.avaya.vp.appruntimevars.AppRuntimeVarsMonitor$MonitorTask.run(AppRuntimeVarsMonitor.java:286)
at java.lang.Thread.run(Thread.java:780)
Caused by: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
at com.ibm.jsse2.j.a(j.java:23)
at com.ibm.jsse2.j.a(j.java:21)
at com.ibm.jsse2.qc.b(qc.java:465)
at com.ibm.jsse2.qc.a(qc.java:451)
at com.ibm.jsse2.qc.h(qc.java:759)
at com.ibm.jsse2.qc.a(qc.java:93)
at com.ibm.jsse2.h.write(h.java:34)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:93)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:151)
at org.apache.axis2.transport.http.AxisRequestEntity
RossYakulis
Joined: Nov 6, 2013
Messages: 2652
Offline
The trace settings from EP override the ddrt.properties settings. They are sent (trace settings) on the query string. So that should work if you enable everything.
RossYakulis
Joined: Nov 6, 2013
Messages: 2652
Offline
have you enabled mutual authentication or anything like that?
BMatchok
Joined: May 26, 2016
Messages: 114
Offline
I dont think it is set up for mutual authentication. I think the key line in the log is the following:
Unable to sendViaPost to url[https://10.27.247.80/axis2/services/VPAppVarsService]

The AEP server is
https://10.27.247.80/

So it looks like Websphere cant communicate with the AEP server. Is there a certificate that Avaya has that allows Websphere to communciate with it ?
RossYakulis
Joined: Nov 6, 2013
Messages: 2652
Offline
Only if you enabled mutual authentication.

You still have yet to produce a trace.log.

not you can always ?ddtrace=true on the query string to force trace as well.
BMatchok
Joined: May 26, 2016
Messages: 114
Offline
This is the URL that AEP is calling:

http://ivr-t.corpads.local/Dispatch/Start?ddtrace=true

So the URL has tracing enabled

The trace logs are very small consisting of one or two lines per call:

This is one trace log:
22/09/2016 12:08:52:274 ERROR - acQFNFCqjx5QHzpIqrpwkHP:/Dispatch : VPClientProxy:VPAppRuntimeVars.getAppRuntimeVars returns null


This is the other trace log:
22/09/2016 12:08:52:258 ERROR - In Progress | session id:avappl001d-2016266160847-6 | Dispatch:Start | null | License server URl Error :java.net.MalformedURLException | null | null |
22/09/2016 12:08:52:258 ERROR - ALARM | session id:avappl001d-2016266160847-6 | Dispatch:Start | | License server URl Error :java.net.MalformedURLException | null | null |


That is the extent of my trace logs
I have trace enabled in AEP with all the options checked but I think due to the fact that parameters are not being passed the logging mechanism doesnt have any way of knowing what level and what to log in the trace. I may be wrong. I attached the app server log
Filename WebsphereLog.txt [Disk] Download
RossYakulis
Joined: Nov 6, 2013
Messages: 2652
Offline
What you are showing "License Server URL Error" is an Alarm and goes into the report.log. I am talking about the OD trace log. On Tomcat you fine it in <tomcat_home>/webapps/<web app name>/data/log/trace.log

Also that error "License Server URL Error" would not cause your application to stop.
Go to:   
Mobile view