View Issue Details

IDProjectCategoryView StatusLast Update
0005823CTT UA Scripts1 - Script Issuepublic2022-08-02 20:04
ReporterV. Monfort Assigned ToAlexander Allmendinger  
PrioritynormalSeverityminorReproducibilityalways
Status assignedResolutionopen 
Summary0005823: Subscription Basic: 023.js: ModifySubscription: PublishingInterval compliance test limited by PublishRequest sending frequency
Description

In the test SubscriptionBasic/023.js, an attempt is made to check the compliance with the PublishingInterval of 2000ms using DataChanges reception after 3 Writes.

Sometimes this test fails with this kind of error:
"Expected a PublishingInterval of 2000 but actual interval was 2441.3333333333335;Expected a value less than 7300 and greater than 5700 but received 7324. "

After some investigation, it seems that the server is not able to send the PublishResponse in time because it receives the PublishRequest late and even by answering immediately cannot comply with the PublishingInterval because he has no Publish token available to do so.
I attached a TCP dump capture that shows that the server responds immediately whereas PublishRequest are sent every 2 seconds by UACTT, in this particular case the tests succeeded but even there we can observe the server is limited by the client PublishingRequest sending frequency which is not the purpose of this test script.

I suggest the client sends more PublishRequest tokens, or increase their frequency or at least provide a new PublishRequet as soon as it received a PublishResponse

TagsNo tags attached.
Attached Files
test.pcap (62,100 bytes)
Files Affected

Activities

Paul Hunkar

2020-07-30 15:37

administrator   ~0012647

Timing of this script depends on the platform on which the CTT is running (a slower platform might have the issue described)

Recommend updated script to use new async call for publish - so multiple publish requests can be sent in advance.

Camille Guérin

2021-03-10 16:31

reporter   ~0014021

I also have the issue with CTT 1.4.9.396
In my case the WriteResponse return GoodCompleteAsynchronously.
After that I also see the CTT sending some corrup ReadRequest
I customized my Server to return Good instead and then the ReadRequests were not corrupted anymore...

corrupt_read.jpg (310,741 bytes)

Issue History

Date Modified Username Field Change
2020-07-24 08:38 V. Monfort New Issue
2020-07-24 08:38 V. Monfort File Added: test.pcap
2020-07-30 15:37 Paul Hunkar Note Added: 0012647
2020-07-30 15:37 Paul Hunkar Assigned To => Alexander Allmendinger
2020-07-30 15:37 Paul Hunkar Status new => assigned
2021-03-10 16:31 Camille Guérin Note Added: 0014021
2021-03-10 16:31 Camille Guérin File Added: corrupt_read.jpg
2021-05-16 14:58 Alexander Allmendinger Target Version => 1.03.341.399
2022-08-02 20:04 Paul Hunkar Project Compliance Test Tool (CTT) Unified Architecture => CTT UA Scripts