hi there,
We have encountered some issues after cut-over for our customer.
They have UCCE, CVP v10.5, SIP Proxy server and have done integration with OBS, their Oracle middle framework with their Back-end Host.
1) They have done a Custom Decision Element created to call their OBS web service and what they noticed from the CVP VXML Activity Log is that the Node was entered, then Transaction Successful but instead of Node Exit, the same Node was executed a second time causing the Transaction to be executed a second time, and then it exits.
From the logs, the issue seem that decision node is called twice. Normally there should be one node enter and one node exit. The issue is that we are having two entry from this node. The code inside the node is not recursive and does not loop.
Session ID : 10.168.125.42.1455711282955.1700.Selfxxx
Application : Selfxxx
Time : 20:16:04.079
Node : OSBCreatexxx
(Attached Source)
As we can see from the Activity log, SB_OSBCreateXxx,enter was called twice before there is an SB_OSBCreateXxx,exit
Below is the logs:
Line 418757: 10.168.125.42.1455711282955.1700.Selfbet,02/17/2016 20:16:04.110,SB_OSBCreateBet,enter,
Line 418758: 10.168.125.42.1455711282955.1700.Selfbet,02/17/2016 20:16:04.110,SB_OSBCreateBet,custom,BetRequest,Meeting[HR] RaceDate[17022016] Race[3] BetAbbr[WIN] Venue[STC] Selection1[06] Units[8]
Line 418759: 10.168.125.42.1455711282955.1700.Selfbet,02/17/2016 20:16:04.110,SB_OSBCreateBet,custom,********,CreateWinBetBMCSRequest
Line 418760: 10.168.125.42.1455711282955.1700.Selfbet,02/17/2016 20:16:04.141,SB_OSBCreateBet,custom,********,CreateWinBetBMCSResponse
Line 418761: 10.168.125.42.1455711282955.1700.Selfbet,02/17/2016 20:16:04.188,SB_OSBCreateBet,custom,CreateWinBetBMCSResponse,MessageStatus[SUCCESS]
Line 418762: 10.168.125.42.1455711282955.1700.Selfbet,02/17/2016 20:16:04.188,SB_OSBCreateBet,custom,Set HostBetValue,40.0
Line 418763: 10.168.125.42.1455711282955.1700.Selfbet,02/17/2016 20:16:04.188,SB_OSBCreateBet,custom,Response,TxnHOSTRESPCODE[00000]
Line 418764: 10.168.125.42.1455711282955.1700.Selfbet,02/17/2016 20:16:04.204,SB_OSBCreateBet,enter,
Line 418765: 10.168.125.42.1455711282955.1700.Selfbet,02/17/2016 20:16:04.204,SB_OSBCreateBet,custom,BetRequest,Meeting[HR] RaceDate[17022016] Race[3] BetAbbr[WIN] Venue[STC] Selection1[06] Units[8]
Line 418766: 10.168.125.42.1455711282955.1700.Selfbet,02/17/2016 20:16:04.204,SB_OSBCreateBet,custom,********,CreateWinBetBMCSRequest
Line 418767: 10.168.125.42.1455711282955.1700.Selfbet,02/17/2016 20:16:04.235,SB_OSBCreateBet,custom,********,CreateWinBetBMCSResponse
Line 418768: 10.168.125.42.1455711282955.1700.Selfbet,02/17/2016 20:16:04.282,SB_OSBCreateBet,custom,CreateWinBetBMCSResponse WebServiceException,javax.xml.ws.soap.SOAPFaultException: [EAI00000000024586838][BEA-380001]CustomBMCSConnectorFunctionalException at CreateWinBetBMCS@ProxyService$SSBK_OSB_Impl$Services$ProxyServices$Sender$CommonServiceSenderPS-RouteTo_BS_From_XQ_Handler||
Line 421796: 10.168.125.42.1455711282955.1700.Selfbet,02/17/2016 20:16:04.282,SB_OSBCreateBet,custom,ErrorResponse,ErrorCode[38161] Desc[Insufficient funds] ReturnBranch[InsufficientFunds]
Line 421797: 10.168.125.42.1455711282955.1700.Selfbet,02/17/2016 20:16:04.282,SB_OSBCreateBet,custom,ErrorResponse,TxnHOSTRESPCODE[38161]
Line 421798: 10.168.125.42.1455711282955.1700.Selfbet,02/17/2016 20:16:04.282,SB_OSBCreateBet,exit,InsufficientFunds
Pls refer to Screenshot1 of Selfxxx activity log.
For the above issue, they have noticed 6 occurrences/calls with such issue happening from CVP server 1.
To add on, they also encounter the above issue with a custom Action Element they have developed for login authentication. But they have done a code work-around to mitigate that issue.
2) They also notice that for the same CVP server 1, there are 6 occurrences of BadFetch HTTP 400 errors occurring at almost the same time (within the same second) but these BadFetch errors happen to other different calls.
They have checked the fetch time between the VXML server and the Back-end host via OSB, seems the return time is very fast, less than 5 secs. So it shouldnt be the FetchTimeout setting which was set to default.
We are not sure whether Issue 1 and Issue 2 have any relation to each other but its just very strange that when we compared the time stamps, these occurrences happen at the same time with each other but for different calls.
Pls contact me directly for more details ..
Rgds,
Accepted Solutions
