10:01, EET
March 16, 2017
Hi all,
I had an issue using the Client SDK v4.3.0 while doing some tests with the Softing dataFeed OPC suite v4.22 (run on demo mode).
At some point I did not get any subscription responses but only the following logging was visible.
2021-03-15 04:29:47,498|UaClient$a|INFO|Got Bad_NoSubscription as a PublishResponse, although we have connected Subscriptions
2021-03-15 04:29:47,529|UaClient$a|INFO|Got Bad_NoSubscription as a PublishResponse, although we have connected Subscriptions
2021-03-15 04:29:47,529|UaClient$a|INFO|Got Bad_NoSubscription as a PublishResponse, although we have connected Subscriptions
2021-03-15 04:29:47,529|UaClient$a|INFO|Got Bad_NoSubscription as a PublishResponse, although we have connected Subscriptions
2021-03-15 04:29:47,529|UaClient$a|INFO|Got Bad_NoSubscription as a PublishResponse, although we have connected Subscriptions
2021-03-15 04:29:47,545|UaClient$a|INFO|Got Bad_NoSubscription as a PublishResponse, although we have connected Subscriptions
Restarting the Client Application (which is based on the Prosys SDK) did not help to solve the issue.
The problem occured until the dataFeed was restarted. After the restart of the dataFeed I was able to get the publish requests.
From Client-SDK point of view, everthing looked quite normal (execpt the INFO logging)
I wonder if there is any possibility to get informed by the Client SDK about the problem, so that I can show a message to the end user that something is wrong and a restart of the OpcUa server is recommended?
Thank you!
14:47, EET
Moderators
February 11, 2020
Hello,
If your Client is receiving this StatusCode as the ServiceResult of the ResponseHeader of a PublishResponse, you can make a new class that implements UaClientListener interface to validate PublishResponses with its validatePublishResponse method. You can add some custom logic to the validation process to notify the user that Bad_NoSubscription StatusCode has been received, though that StatusCode by itself doesn’t imply that the PublishResponse is invalid and thus you should still have the method return true, unless there is something else wrong with the PublishResponse. Take a look at SampleConsoleClient and its MyUaClientListener for an example of how to implement UaClientListener interface and use it in a Client application.
However, if your Client receives this StatusCode in a ServiceFault, then the stack layer handles the error internally and no custom logic can be added to processing the ServiceFault.
Most Users Ever Online: 1919
Currently Online:
20 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Heikki Tahvanainen: 402
hbrackel: 144
rocket science: 88
pramanj: 86
Francesco Zambon: 83
Ibrahim: 78
Sabari: 62
kapsl: 57
gjevremovic: 49
Xavier: 43
Member Stats:
Guest Posters: 0
Members: 735
Moderators: 7
Admins: 1
Forum Stats:
Groups: 3
Forums: 15
Topics: 1523
Posts: 6449
Newest Members:
rust, christamcdowall, redaahern07571, nigelbdhmp, travistimmons, AnnelCib, dalenegettinger, howardkennerley, Thomassnism, biancacraft16Moderators: Jouni Aro: 1026, Pyry: 1, Petri: 0, Bjarne Boström: 1026, Jimmy Ni: 26, Matti Siponen: 346, Lusetti: 0
Administrators: admin: 1