Service Virtualization

  • 1.  Lisa is sending No match found response after correct response

    Posted Jun 23, 2017 03:13 AM

    Hello Kevin and all,

     

    We are facing one more issue, that when Lisa is getting request message in request then Lisa is responding VSE not match error response as well with success response. Not getting why this is happening.Please find some part of logs below.

     

    2017-06-22 21:01:23,670Z (22:01)[APS [VS_APS_Run]/1] INFO  - Inbound Request {"id":0,"operation":"ApplyPaymentPostingRequest","arguments":{"accountingTransaction_description":"Anil LBG Co F/FLOW TFR   5110000402","accountingTransaction_originationDate":"2014-03-24T00:00:00","accountingTransaction_initiatesMonetaryPosting_accountingEffectType":"Debit","accountingTransaction_initiatesMonetaryPosting_effectiveDate":"2014-03-24T00:00:00","accountingTransaction_initiatesMonetaryPosting_amount_theCurrencyAmount":"2000.67","accountingTransaction_initiatesMonetaryPosting_amount_theCurrencyCode":"GBP","accountingTransaction_targets_objectReference_accountNumber":"17070460","accountingTransaction_targets_isManagedByOrgUnit_sortCode":"306747","accountingTransaction_targets_customer_customerName_nameText":"Bhakti Chandrakant","paymentPostingInstruction_objectReference_refId":"8520096113","paymentPostingInstruction_objectReference_alternateId_attributeString":"ACCOUNT_TYPE","paymentPostingInstruction_objectReference_alternateId_value_1":"Personal Account","paymentPostingInstruction_objectReference_alternateId_value_2":"Inbound","paymentPostingInstruction_scheme_schemeName":"CHAPS","paymentPostingInstruction_transactionType":"Normal","ServiceRequest_ServiceName":"http://www.lloydstsb.com/Schema/ArrangementAccountProcessing/IFW/ArrangementAccountProcessingService","ServiceRequest_Action":"N","ServiceRequest_From":"TMH_TxnBus","ServiceRequest_MessageId":"8520096113","Security_UsernameToken_Username":"TMH_TxnBus","Security_UsernameToken_Password":"","ContactPoint_ContactPointType":"003","ContactPoint_ContactPointId":"0000306747","ContactPoint_ApplicationId":"AL05810","ContactPoint_InitialOriginatorId":"Transaction Bus","ContactPoint_OperatorType":"Customer"}}
    2017-06-22 21:01:23,670Z (22:01)[APS [VS_APS_Run]/1] INFO  - No Session ID No session identified
    2017-06-22 21:01:23,670Z (22:01)[APS [VS_APS_Run]/1] INFO  - Stateless Match Transaction: {"id":2,"navigationTolerance":"<stateless>","request":{"id":3,"matchTolerance":"OPERATION","operation":"ApplyPaymentPostingRequest","arguments":{"accountingTransaction_description":"Anil LBG Co F/FLOW TFR 5110000401","accountingTransaction_originationDate":"2016-01-12T00:00:00","accountingTransaction_initiatesMonetaryPosting_accountingEffectType":"Debit","accountingTransaction_initiatesMonetaryPosting_effectiveDate":"2016-01-12T00:00:00","accountingTransaction_initiatesMonetaryPosting_amount_theCurrencyAmount":"2000.67","accountingTransaction_initiatesMonetaryPosting_amount_theCurrencyCode":"GBP","accountingTransaction_targets_objectReference_accountNumber":"30000001","accountingTransaction_targets_isManagedByOrgUnit_sortCode":"301234","accountingTransaction_targets_customer_customerName_nameText":"THE LOFT LOUNGE LT","paymentPostingInstruction_objectReference_refId":"4169219223","paymentPostingInstruction_objectReference_alternateId_attributeString":"ACCOUNT_TYPE","paymentPostingInstruction_objectReference_alternateId_value_1":"Personal Account","paymentPostingInstruction_objectReference_alternateId_value_2":"Inbound","paymentPostingInstruction_scheme_schemeName":"CHAPS","paymentPostingInstruction_transactionType":"Normal","ServiceRequest_ServiceName":"http://www.lloydstsb.com/Schema/ArrangementAccountProcessing/IFW/ArrangementAccountProcessingService","ServiceRequest_Action":"N","ServiceRequest_From":"TMH_TxnBus","ServiceRequest_MessageId":"4169219223","Security_UsernameToken_Username":"TMH_TxnBus","Security_UsernameToken_Password":"","ContactPoint_ContactPointType":"003","ContactPoint_ContactPointId":"0000301234","ContactPoint_ApplicationId":"AL05810","ContactPoint_InitialOriginatorId":"Transaction Bus","ContactPoint_OperatorType":"Customer"}}}
    2017-06-22 21:01:23,670Z (22:01)[APS [VS_APS_Run]/1] INFO  - Response Lookup Completed
    2017-06-22 21:01:23,677Z (22:01)[APS [VS_APS_Run]/1] INFO  - Sent Message payload   <?xml version="1.0" ?>
     <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://www.lloydstsb.com/Schema/Infrastructure/SOAP" xmlns:oas="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:ifw="http://www.lloydstsb.com/Schema/ArrangementAccountProcessing/IFW" xmlns:ifw2="http://xml.lloydsbanking.com/Schema/Enterprise/InformationTechnology/ESB/IFWXML" xmlns:ifw1="http://www.lloydstsb.com/Schema/Enterprise/IFWXML_Extended_Classes" xmlns:ifw3="http://xml.lloydsbanking.com/Schema/Enterprise/InformationTechnology/ESB/IFWXML_Common" xmlns:ifw4="http://xml.lloydsbanking.com/Schema/Enterprise/InformationTechnology/ESB/IFWXML_Event" xmlns:ifw5="http://xml.lloydsbanking.com/Schema/Enterprise/InformationTechnology/ESB/IFWXML_InvolvedParty" xmlns:ifw6="http://xml.lloydsbanking.com/Schema/Enterprise/InformationTechnology/ESB/IFWXML_Arrangement" xmlns:ifw7="http://xml.lloydsbanking.com/Schema/Enterprise/InformationTechnology/ESB/IFWXML_AccountingUnit" xmlns:ifw8="http://xml.lloydsbanking.com/Schema/Enterprise/InformationTechnology/ESB/IFWXML_AccountingTransaction" xmlns:ifw9="http://xml.lloydsbanking.com/Schema/Enterprise/InformationTechnology/ESB/IFWXML_Product" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
     <SOAP-ENV:Header>
     <soap:ServiceRequest soap:mustReturn="true">
      <soap:ServiceName>http://www.lloydstsb.com/Schema/ArrangementAccountProcessing/IFW/ArrangementAccountProcessingService</soap:ServiceName>
     <!-- Action is the Stand-in Processing Indicator Flag
      -->
      <soap:Action>N</soap:Action>
      <soap:From>TMH_TxnBus</soap:From>
     <!-- Optional:
      -->
      <soap:MessageId>6069209009</soap:MessageId>
      </soap:ServiceRequest>
     <oas:Security mustReturn="true">
    <oas:UsernameToken oas:UNPMechanismType="LTPA" oas:UserType="047" Id="LloydsTSBSecurityToken">
      <oas:Username>TMH_TxnBus</oas:Username>
      <oas:Password PasswordEnumType="Digest">String</oas:Password>
      </oas:UsernameToken>
      </oas:Security>
     <soap:ContactPoint soap:mustReturn="true">
      <soap:ContactPointType>003</soap:ContactPointType>
      <soap:ContactPointId>0000306747</soap:ContactPointId>
      <soap:ApplicationId>AL05810</soap:ApplicationId>
     <!-- Optional:
      -->
      <soap:InitialOriginatorType>String</soap:InitialOriginatorType>
     <!-- Optional:
      -->
      <soap:InitialOriginatorId>Transaction Bus</soap:InitialOriginatorId>
      <soap:OperatorType>Customer</soap:OperatorType>
      </soap:ContactPoint>
      </SOAP-ENV:Header>
     <SOAP-ENV:Body>
     <ifw:ApplyPaymentPostingResponse>
     <responseHeader>
      <ifw1:id>ID_1</ifw1:id>
      <ifw1:cmdStatus>ok</ifw1:cmdStatus>
     <ifw1:resultConditions>
      <ifw2:severityCode>0</ifw2:severityCode>
      <ifw2:reasonCode>0</ifw2:reasonCode>
      <ifw2:reasonText>success</ifw2:reasonText>
      <ifw2:reasonDetail>success</ifw2:reasonDetail>
      </ifw1:resultConditions>
     <ifw1:genericReference>
      <ifw2:type>ABC</ifw2:type>
      <ifw2:refid>6069209009</ifw2:refid>
      </ifw1:genericReference>
      </responseHeader>
     <contraAccountTransaction xsi:type="ifw8:Transfer">
     <ifw4:hasEventType>
      <ifw3:name>Principal Debit</ifw3:name>
      </ifw4:hasEventType>
     <ifw8:initiatesMonetaryPosting>
      <ifw7:accountingEffectType>Debit</ifw7:accountingEffectType>
      </ifw8:initiatesMonetaryPosting>
     <ifw8:targets>
     <ifw3:objectReference xsi:type="ifw6:ProductArrangementObjectReference">
      <ifw6:accountNumber>17070460</ifw6:accountNumber>
      </ifw3:objectReference>
     <ifw6:isManagedByOrgUnit xsi:type="ifw5:Branch">
      <ifw5:sortCode>306747</ifw5:sortCode>
      </ifw6:isManagedByOrgUnit>
      </ifw8:targets>
      </contraAccountTransaction>
      </ifw:ApplyPaymentPostingResponse>
      </SOAP-ENV:Body>
      </SOAP-ENV:Envelope>
    2017-06-22 21:01:31,709Z (22:01)[APS [VS_APS_Run]/10] INFO  - Sent Message payload <?xml version="1.0" encoding="UTF-8"?>
    <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
      <S:Body>
        <S:Fault xmlns:ns3="http://www.w3.org/2003/05/soap-envelope">
          <faultcode>S:Server</faultcode>
          <faultstring>The LISA VSE service could not match your request to a recorded request. Consider expanding your service image.</faultstring>
          <detail>
            <ns2:exception xmlns:ns2="http://jax-ws.dev.java.net/" class="java.lang.Exception">
              <message>The LISA VSE service could not match your request to a recorded request. Consider expanding your service image.</message>
              <ns2:stackTrace>
              </ns2:stackTrace>
            </ns2:exception>
          </detail>
        </S:Fault>
      </S:Body>
    </S:Envelope>



  • 2.  Re: Lisa is sending No match found response after correct response

    Posted Jun 23, 2017 05:25 PM

    For the record, Shivam, I'm not really support and I try to let other people handle forum posts that don't specifically involve MQ or JMS, and I'm not sure this does.

     

    The second response, the "error" response, is being sent by a different thread, "APS [VS_APS_Run]/10", versus "APS [VS_APS_Run]/1".  Are you sure there isn't more to this log, above the excerpt you included, that shows that other thread receiving a second request?



  • 3.  Re: Lisa is sending No match found response after correct response
    Best Answer

    Posted Jun 23, 2017 06:14 PM

    I agree with Kevin. You are looking at two different responses to two different requests.

     

    The log files contain output from every thread that is running. So, you are going to need to do some log file stitching or switch to the Portal view and review the matched transactions for the incoming requests.

     

    The following messages in the log file excerpt are related to APS_Run, thread 1:

    2017-06-22 21:01:23,670Z (22:01)[APS [VS_APS_Run]/1] INFO  - Inbound Request {"id":0,"operation":...

    2017-06-22 21:01:23,670Z (22:01)[APS [VS_APS_Run]/1] INFO  - No Session ID No session identified
    2017-06-22 21:01:23,670Z (22:01)[APS [VS_APS_Run]/1] INFO  - Stateless Match Transaction: {"id":2,"navigationTolerance":"<stateless>","request":{"id":3,"matchTolerance": "OPERATION",

    2017-06-22 21:01:23,670Z (22:01)[APS [VS_APS_Run]/1] INFO  - Response Lookup Completed
    2017-06-22 21:01:23,677Z (22:01)[APS [VS_APS_Run]/1] INFO  - Sent Message payload

     

    This next entry is related to a request processed by APS_Run, thread 10. Notice the thread number is different.

    2017-06-22 21:01:31,709Z (22:01)[APS [VS_APS_Run]/10] INFO  - Sent Message payload

     

    You would need to manually cut / copy / paste the vse.log, vse_matches.log and VS_APS_Run.log for the timeslice range 21:01:23 to 21:01:32, the virtual service name (VS_APS_Run), and the Thread Number to determine exactly what happened in your service.

     

    Based on the log file excerpt you posted, there was another incoming request processed by thread 10 that is not shown. Look for Inbound Request, Stateless Match displays related to Thread 10 to see what the request looked like. 



  • 4.  Re: Lisa is sending No match found response after correct response

    Posted Jun 27, 2017 02:35 AM

    Thanks I will check that and will let you know in case of any query.

     

    Cheers..

    Shivam Garg