View Issue Details

IDProjectCategoryView StatusLast Update
0004643Compliance Test Tool (CTT) Unified Architecture1 - Script Issuepublic2022-10-12 16:47
ReporterBernd Edlinger Assigned ToAlexander Allmendinger  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionduplicate 
Product Version1.03.341.384 
Summary0004643: Subscription Services/Subscription Publish Min 02/003.js fails due to timing issue
Description

CTT: 1.03.341.385 and 1.03.340.380

This test case fails due to a race condition between the server's publishing interval
and the write request.

Error: Publish() response did not complete within the expected time-frame.
Expected a value less than <11000> and greater than <9000> but received <16251>.

The test starts a subscription with Publishing Interval = 5.000s + MaxKeepAliveCount = 1

2 Publish requests are sent initially,
the first write is sent after 5.020s, and the publishing thread wakes up shortly after
the write. So the first publish response collects the written values, and at the
time when the test expects the second publish response, there are no new data,
the keepalive happens after another 5.000s

Suggest to add a 500ms delay before sending the write request,
thus allow 10% drift in the publishing interval.

    // write to ALL items
    PublishHelper.WaitInterval( { Items: items, Subscription: subscription } );
    UaDateTime.CountDown({ Msecs: 500, SuppressMessage: true }); // added an additional 500ms delay here
    WriteHelper.Session.write( writeRequest, writeResponse );
    if (writeResponse.ResponseHeader.ServiceResult.isBad()) return (false);
TagsNo tags attached.
Files Affected

Relationships

duplicate of 0004459 closedAlexander Allmendinger Performance issue with Subscription Publish Min 02/002.js and 003.js 

Activities

Paul Hunkar

2019-03-07 15:32

administrator   ~0010027

Suspect that initial values are missing in server

Bernd Edlinger

2019-03-20 07:48

reporter   ~0010072

No, the issue is the write in the script changes the values before the initial values are reported,
therefore the next publish response is not sent, since no new values are there.

Sebastian Allmendinger

2022-03-15 06:35

developer   ~0016370

Resolved with Mantis 4459

Paul Hunkar

2022-10-12 16:47

administrator   ~0018017

reviewed in call, agree it is a duplicate or other issue, other issue is closed, closing this issue

Issue History

Date Modified Username Field Change
2019-02-26 10:32 Bernd Edlinger New Issue
2019-03-07 15:31 Paul Hunkar Assigned To => Alexander Allmendinger
2019-03-07 15:31 Paul Hunkar Status new => assigned
2019-03-07 15:32 Paul Hunkar Note Added: 0010027
2019-03-20 07:48 Bernd Edlinger Note Added: 0010072
2022-03-15 06:35 Sebastian Allmendinger Status assigned => resolved
2022-03-15 06:35 Sebastian Allmendinger Resolution open => no change required
2022-03-15 06:35 Sebastian Allmendinger Note Added: 0016370
2022-08-02 20:23 Paul Hunkar Project Compliance Test Tool (CTT) Unified Architecture => CTT UA Scripts
2022-08-02 20:23 Paul Hunkar Project CTT UA Scripts => .NET API
2022-08-02 20:23 Paul Hunkar Category 1 - Script Issue => Api Change
2022-08-04 14:24 Paul Hunkar Project .NET API => Compliance Test Tool (CTT) Unified Architecture
2022-10-12 16:46 Paul Hunkar Relationship added duplicate of 0004459
2022-10-12 16:47 Paul Hunkar Resolution no change required => duplicate
2022-10-12 16:47 Paul Hunkar Category Api Change => 1 - Script Issue
2022-10-12 16:47 Paul Hunkar Status resolved => closed
2022-10-12 16:47 Paul Hunkar Note Added: 0018017