Avatar

Please consider registering
guest

sp_LogInOut Log In sp_Registration Register

Register | Lost password?
Advanced Search

— Forum Scope —




— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

sp_Feed Topic RSS sp_TopicIcon
"Server sent a previously acknowledged sequence number" ?
February 8, 2023
12:07, EET
Avatar
Oleksandr
Member
Members
Forum Posts: 34
Member Since:
February 14, 2020
sp_UserOfflineSmall Offline

Hello
we have the problem that the subscription will not work after the reconnect to the OPC UA server (Siemens PLC). Can you please explain what the entries in the prosys.log mean?
Thanks in advance.
Oleksandr

prosys.log:
30-11-2022 09:58:03.992 [INFO] com.prosysopc.ua.typedictionary.TypeDictionary:368 – TypeDictionary initialized successfully
01-12-2022 07:26:40.978 [INFO] com.prosysopc.ua.stack.transport.tcp.io.SecureChannelTcp:378 – 1248186086 Closed
01-12-2022 07:26:40.978 [INFO] com.prosysopc.ua.stack.transport.tcp.io.TcpConnection:1490 – /10.63.17.206:4840 Closed
01-12-2022 07:26:40.978 [INFO] com.prosysopc.ua.stack.transport.tcp.io.TcpConnection:515 – /10.63.17.206:4840 Closed (expected)
01-12-2022 07:26:50.978 [INFO] com.prosysopc.ua.stack.transport.tcp.io.TcpConnection:998 – /10.63.17.206:4840 Connecting
01-12-2022 07:26:51.025 [INFO] com.prosysopc.ua.stack.transport.tcp.io.TcpConnection:1261 – Connected (non-reverse), handshake completed, local=/10.110.172.35:56120, remote=/10.63.17.206:4840
01-12-2022 07:26:54.525 [WARN] com.prosysopc.ua.typedictionary.DataTypeDictionaryComposition:43 – More than one GeneratedDataTypeDictionary contains the same dictionary TargetNamespace http://opcfoundation.org/UA/
01-12-2022 07:26:54.525 [WARN] com.prosysopc.ua.typedictionary.DataTypeDictionaryComposition:43 – More than one GeneratedDataTypeDictionary contains the same dictionary TargetNamespace http://opcfoundation.org/UA/GDS/
01-12-2022 07:26:55.650 [INFO] com.prosysopc.ua.client.Subscription:964 – Missing NotificationMessage (SequenceNumber=1) no longer available from server. Target SequenceNumber=34830
01-12-2022 07:26:55.650 [INFO] com.prosysopc.ua.client.Subscription:964 – Missing NotificationMessage (SequenceNumber=2) no longer available from server. Target SequenceNumber=34830
01-12-2022 07:26:55.650 [INFO] com.prosysopc.ua.client.Subscription:964 – Missing NotificationMessage (SequenceNumber=3) no longer available from server. Target SequenceNumber=34830
…….

01-12-2022 07:26:56.838 [INFO] com.prosysopc.ua.client.Subscription:964 – Missing NotificationMessage (SequenceNumber=34829) no longer available from server. Target SequenceNumber=34830
01-12-2022 07:26:56.838 [INFO] com.prosysopc.ua.client.Subscription:964 – Missing NotificationMessage (SequenceNumber=34830) no longer available from server. Target SequenceNumber=34830
01-12-2022 07:28:14.838 [WARN] com.prosysopc.ua.typedictionary.TypeDictionary:759 – Could not parse the following Structure definitions from typedictionaries: [http://www.siemens.com/simatic-s7-opcua:3400, http://www.siemens.com/simatic-s7-opcua:3500%5D
01-12-2022 07:28:14.838 [INFO] com.prosysopc.ua.typedictionary.TypeDictionary:368 – TypeDictionary initialized successfully
01-12-2022 07:28:15.057 [WARN] com.prosysopc.ua.client.Subscription:1925 – Server sent a previously acknowledged sequence number 1 for Subscription 565829124
01-12-2022 07:28:17.667 [WARN] com.prosysopc.ua.client.Subscription:1925 – Server sent a previously acknowledged sequence number 2 for Subscription 565829124
01-12-2022 07:28:48.043 [WARN] com.prosysopc.ua.client.Subscription:1925 – Server sent a previously acknowledged sequence number 3 for Subscription 565829124
01-12-2022 07:29:18.450 [WARN] com.prosysopc.ua.client.Subscription:1925 – Server sent a previously acknowledged sequence number 3 for Subscription 565829124
…..

01-12-2022 10:56:59.557 [WARN] com.prosysopc.ua.client.Subscription:1925 – Server sent a previously acknowledged sequence number 638 for Subscription 565829124
01-12-2022 10:56:59.963 [WARN] com.prosysopc.ua.client.Subscription:1925 – Server sent a previously acknowledged sequence number 639 for Subscription 565829124

February 8, 2023
16:01, EET
Avatar
Matti Siponen
Moderator
Members

Moderators
Forum Posts: 328
Member Since:
February 11, 2020
sp_UserOfflineSmall Offline

Hello,

Which version of the Prosys OPC UA SDK for Java are you using? The latest version is 4.10.2 and if you’re using an older version you could update to the latest version if possible and check if that has fixed the issue.

February 15, 2023
12:25, EET
Avatar
Oleksandr
Member
Members
Forum Posts: 34
Member Since:
February 14, 2020
sp_UserOfflineSmall Offline

Hello,
Version 4.2.0-955.
unfortunately I can’t update it. It has to stay with the version.
Please explain the meaning of the error.
Is the problem on the OPC UA server side or on my client?
can it be that the server is overloaded and that’s why the problem occurs?
Thanks you in advance.
Oleksandr

February 15, 2023
15:29, EET
Avatar
Matti Siponen
Moderator
Members

Moderators
Forum Posts: 328
Member Since:
February 11, 2020
sp_UserOfflineSmall Offline

Hello,

These messages are related to a Subscription recovering from a communication break between the Client and the Server. The Client is asking the Server to Republish missing PublishResponses and “Missing NotificationMessage” log entries indicate the Server no longer has them. On the other hand, “Server sent a previously acknowledged sequence number” log entries mean that the Server is sending PublishResponses with sequence numbers that the Client has already received.

Prosys OPC UA SDK for Java version 4.2.0 is very old, so it is possible that errors in the SDK related to Subscriptions recovering from communication breaks have been fixed. Critical CVE https://www.prosysopc.com/blog/invalid-server-nonces-vulnerability/ has also been fixed since version 4.2.0. Is there a reason why you can’t update from version 4.2.0?

Historically there have been problems with Siemens OPC UA Servers, which have been fixed in a later firmware versions. Therefore, please verify that the PLC is running the latest firmware version. If not, update to the latest firmware version if possible.

Also, are you handling reconnects using automatic reconnecting or manually? If you’re handling them manually, make sure that the automatic reconnecting has been disabled by calling setAutoReconnect(false) for the UaClient instance. Handling reconnecting both manually and automatically at the same time can cause unexpected errors. The current version of the SDK would prevent calling reconnet manually while the automatic reconnecting is in use.

Forum Timezone: Europe/Helsinki

Most Users Ever Online: 518

Currently Online:
21 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

Heikki Tahvanainen: 402

hbrackel: 138

pramanj: 86

rocket science: 81

Francesco Zambon: 81

Ibrahim: 76

Sabari: 62

kapsl: 57

gjevremovic: 49

Xavier: 43

Member Stats:

Guest Posters: 0

Members: 713

Moderators: 7

Admins: 1

Forum Stats:

Groups: 3

Forums: 15

Topics: 1476

Posts: 6294

Newest Members:

mariam6210, donblanchard632, HowardLon, delilahhuggard, salvadorcolby69, HelenImpar, MnoioDat, babuinsobaka, Miikka Mikkonen, rickeylipinski

Moderators: Jouni Aro: 1015, Pyry: 1, Petri: 0, Bjarne Boström: 986, Jimmy Ni: 26, Matti Siponen: 328, Lusetti: 0

Administrators: admin: 1