Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Multiple SOAPCALLs where single call expected

Description

Multiple SOAPCALL invocations with same request appear when only a single one is expected.

Example:

The module concerned are

  UKServices_V10D.MapViewPerilsDirectSearchService

  UKServices_V10D.MapViewPerilsAmbientalAALService

  UKServices_V10D.MapViewPerilsFloodREService

 The behaviour/evaluations are correct but looking at the roxie logs I see multiple SOAPCALL invocations with the same request and appears service is getting called multiple times.

 Possibly multiple evaluations are happening in the following section of code:

 For the Ambiental call, if call with UPRN does not return a result it will do another call with Postcode search.

For floodRe, should only ever be one call at most.

I have attached a ZAP and roxie log.

 

Please check and advise how we can suppress the additional calls.

If required I can elaborate/demo interactively.

 

Conclusion

None

Activity

Show:

Parminder Sembi February 11, 2022 at 2:53 PM

Log is available but not attached yo ticket, has test PII

Parminder Sembi February 11, 2022 at 2:51 PM

Parminder,

Thank you for the example.  I think there are a couple of different things going on:

 

  1. The first is that datasets are resourced much better than rows.

 

So in UKServices_V10D\MapViewPerilsDirectSearchService.ecl there is the following code:

 

MapViewPerilsResponse := MAP(MatchIndocator = 'BM' => DATASET(ROW(getMapViewPerilsIfBM(Call_MapViewSaltKey[1]))),

 

re-expressing it as:

 

MapViewPerilsDirectResponse := MAP(MatchIndicator = 'BM' => DATASET(PROJECT(recs, getMapViewPerilsIfBM(LEFT))[1]),

 

removes several of the SOAPCALLS.

 

  1. The second problem looks like a problem with the code generator.  I don't think it is very easy to work around in the ecl code.  Please can you create a jira - and I will experiment with a fix.

 

Thanks,

Gavin.

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Fix versions

Pull Request URL

Created February 11, 2022 at 2:49 PM
Updated February 17, 2022 at 3:41 PM
Resolved February 17, 2022 at 3:41 PM