View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0004472Compliance Test Tool (CTT) Unified Architecture5 - General Problempublic2018-11-22 13:412019-08-02 03:46
ReporterHannes Mezger Assigned ToHannes Mezger  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
PlatformPCOSWindowsOS Version8.1
Product Version1.03.341.383 
Target Version1.03.341.384Fixed in Version1.03.341.390 
Summary0004472: Subscription Services/Subscription Publish Min 02/003.js
Description

Tested with UnifiedAutomation C++ Demoserver 1.6.3

Following error is thrown:

Publish() response did not complete within the expected time-frame.
Expected a value greater than <4500> and less than <5500>; but received <1997>.

Looking at the backtrace, the publish in question is the first one. The calls are as follows:

2018-11-22 14:29:12.198 ---> CreateSubscription
2018-11-22 14:29:12.199 <--- CreateSubscription
2018-11-22 14:29:14.185 ---> CreateMonitoredItems
2018-11-22 14:29:14.352 <--- CreateMonitoredItems
2018-11-22 14:29:15.301 ---> Publish 1
2018-11-22 14:29:15.313 ---> Publish 2
2018-11-22 14:29:17.256 <--- Publish 1
2018-11-22 14:29:22.201 <--- Publish 2

According to this, the server behaves correctly: the subscription is created with publishing interval 5000 at second 12.2, so the first publish response is to be expected at around 17.2, which is the case for the first publish response.

TagsNo tags attached.
Files Affected

Relationships

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

Activities

Bernd Edlinger

2018-11-22 21:00

reporter   ~0009629

This is exactly what I observed as well, see 0004459 for a fix.

Alexander Allmendinger

2018-12-19 10:41

developer   ~0009738

Please check purposed fix in related Mantis manually or with the new Beta.

Alexander Allmendinger

2019-07-30 09:02

developer   ~0010638

As this issue cannot be reproduced with the latest beta we consider this being fixed by fixes checed in for MantisId=4459

Paul Hunkar

2019-08-02 03:46

administrator   ~0010660

Reviewed in cmp call 8/1/2019

[note this issue is more of a duplicate then a no-change required]

Issue History

Date Modified Username Field Change
2018-11-22 13:41 Hannes Mezger New Issue
2018-11-22 13:41 Hannes Mezger Status new => assigned
2018-11-22 13:41 Hannes Mezger Assigned To => Alexander Allmendinger
2018-11-22 13:41 Hannes Mezger Issue generated from: 0004471
2018-11-22 21:00 Bernd Edlinger Note Added: 0009629
2018-12-19 10:35 Alexander Allmendinger Relationship added related to 0004459
2018-12-19 10:41 Alexander Allmendinger Note Added: 0009738
2018-12-19 10:41 Alexander Allmendinger Assigned To Alexander Allmendinger => Hannes Mezger
2018-12-19 10:41 Alexander Allmendinger Status assigned => feedback
2019-01-07 16:20 Paul Hunkar Target Version => 1.03.341.384
2019-01-28 14:14 Paul Hunkar Category General Problem => 4 - General Problem
2019-01-28 14:15 Paul Hunkar Category 4 - General Problem => 5 - General Problem
2019-07-30 09:02 Alexander Allmendinger Status feedback => resolved
2019-07-30 09:02 Alexander Allmendinger Resolution open => no change required
2019-07-30 09:02 Alexander Allmendinger Fixed in Version => 1.03.341.390
2019-07-30 09:02 Alexander Allmendinger Note Added: 0010638
2019-08-02 03:46 Paul Hunkar Status resolved => closed
2019-08-02 03:46 Paul Hunkar Note Added: 0010660