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
Invalid sequence number in availableSequenceNumbers list received from server
February 5, 2016
9:28, EET
Avatar
usam95
Member
Members
Forum Posts: 4
Member Since:
November 23, 2015
sp_UserOfflineSmall Offline

Hello,
my OPC-UA-Client creates a Subscription, a couple of MonitoredDataItems and assigns them to buffers. Druring getting the data from server a receive also the following notification e.g. “Invalid sequence number 125 in availableSequenceNumbers list received from server. Current SequenceNumber=124”. I’m getting this information about every five minutes and aslo the current and invalid SequenceNumbers are not the same in each notification.
What does this notification mean and how could I solve this problem

Br,
Usam

February 5, 2016
13:53, EET
Avatar
Heikki Tahvanainen
Member
Members
Forum Posts: 402
Member Since:
April 17, 2013
sp_UserOfflineSmall Offline

Hello,

That logging is intended to indicate that invalid sequence number was detected by the client. The client then deletes this sequence number.

In this scenario this log line should not appear: it’s clear that the SDK is handling message 124 while message 125 (and/or maybe 126) have already arrived to be handled next. The method that produces this log line also contains a check to see whether or not this sequence number corresponds to actual publish response message. This check should prevent this situation and mentioned log line from happening. It’s possible that this is a bug in the SDK.

The consequence in this case is that the sequence number 125 is removed from the client side available sequence numbers. This should only affect the republish service. Your application is probably not influenced by this at all.

and how could I solve this problem

If this is classified as a bug in the SDK, then it will be fixed in the next version of the SDK. In the meantime, you can just ignore that log line. If you really need to get that log line to disappear, you can set logging level of com.prosysopc.ua.client.Subscription package to WARN, ERROR or OFF. However, I would not suggest that as you may miss some important log lines.

Thanks for noticing and reporting this!

April 4, 2016
12:27, EEST
Avatar
jun
Member
Members
Forum Posts: 7
Member Since:
June 18, 2015
sp_UserOfflineSmall Offline

Hello,

we have a similar issue, but the sequence numbers mentioned in the log-entry are way further apart.

We are using the client Java SDK 2.2.2 and we have the following use case:
The application creates 60+ OPCUA clients, each having exactly 1 subscription with <10 nodes connecting to one commercial OPCUA server.

We see these INFO-level entries in our log:

2016-04-04 11:13:42,701 INFO [PublishTask-….OPCUAClient@1d61f85e][Subscription] – Invalid sequence number 51 in availableSequenceNumbers list received from server. Current SequenceNumber=1
2016-04-04 11:13:42,702 INFO [PublishTask-…..OPCUAClient@2f82fd1][Subscription] – Invalid sequence number 712 in availableSequenceNumbers list received from server. Current SequenceNumber=38
2016-04-04 11:13:42,703 INFO [PublishTask-…..OPCUAClient@208ed0b8][Subscription] – Invalid sequence number 94 in availableSequenceNumbers list received from server. Current SequenceNumber=11
2016-04-04 11:13:42,705 INFO [PublishTask-…..OPCUAClient@4bee1207][Subscription] – Invalid sequence number 772 in availableSequenceNumbers list received from server. Current SequenceNumber=182
2016-04-04 11:13:42,798 INFO [PublishTask-…..OPCUAClient@52020fdd][Subscription] – Invalid sequence number 9454 in availableSequenceNumbers list received from server. Current SequenceNumber=511

Since the numbers in the same log-entry are so unrelated to each other, I assume that it’s a different cause than the above mentioned issue, but maybe they are related.

Is there a way to find out if the issue is with the client or the server?

Thanks in advance!

April 4, 2016
13:53, EEST
Avatar
Jouni Aro
Moderator
Moderators
Forum Posts: 1026
Member Since:
December 21, 2011
sp_UserOfflineSmall Offline

It is a bit difficult to investigate, but sounds like the issue is somehow caused by the server, which is reporting “odd” sequence numbers in the list of available ones.

You could try to enable more logging on the client side, to reveal the details of the communication, so that you could see what the server is sending and what leads to this situation.

In any case, this is not a severe problem. Therefore it is only reported on the INFO level. But it may indicate a problem in the server.

July 22, 2016
18:09, EEST
Avatar
in-fke
Member
Members
Forum Posts: 36
Member Since:
June 8, 2016
sp_UserOfflineSmall Offline

We also get this using Simulation Server 2.2.2-1.0.9
1. subscribe / connect while server is down (setKeepSubscriptions() was not called – don’t know what the default is)
2. shut down server: several “Invalid sequence number” messages from client
3. start up server: even more “Invalid sequence number” messages from client

Not sure if even a simpler setup would also cause this.

July 26, 2016
14:13, EEST
Avatar
Heikki Tahvanainen
Member
Members
Forum Posts: 402
Member Since:
April 17, 2013
sp_UserOfflineSmall Offline

Hello,

This is a known bug at the moment. This is not related to Simulation Server, it’s a client side issue in the SDK and happens with all servers.

In above situation 2. this can be seen in logging statements like this:

07/26/2016 13:47:37.899 INFO Invalid sequence number 12 in availableSequenceNumbers list received from server. Current SequenceNumber=0

In above situation 3. this can be seen in logging statements like this:

07/26/2016 13:48:10.015 INFO Invalid sequence number 12 in availableSequenceNumbers list received from server. Current SequenceNumber=4

This is an unfortunate situation, but luckily this should not cause too much trouble for you. This should only affect the republish service and your application is probably not influenced by this at all. If you believe that you have an application scenario where this causes problems and you would like to have an instant fix, then please contact us at uajava-support@prosysopc.com. Otherwise you can just wait for the next SDK release where this should be fixed.

September 30, 2016
18:15, EEST
Avatar
in-fke
Member
Members
Forum Posts: 36
Member Since:
June 8, 2016
sp_UserOfflineSmall Offline

We have an up-to-date case. The problem it causes is that log is spammed (46913 messages is roughly 80 minutes) and that we are unsure whether we are “in sync” with our subscriptions. I’ll get in touch with you directly…

This is a log excerpt (Server was restarted)

2016-09-30 14:55:04,488 WARN io.SecureChannelTcp:? Connection failed: Bad_ConnectionRejected (code=0x80AC0000, description=”2158755840, Connection refused: connect”)
2016-09-30 14:55:05,504 ERROR *disclosed*Bad_ConnectionRejected (code=0x80AC0000, description=”2158755840, Connection refused: connect”)
caused by:
Bad_ConnectionRejected (code=0x80AC0000, description=”2158755840, Connection refused: connect”)
caused by:
Connection refused: connect
2016-09-30 14:55:33,518 INFO client.UaClient:? Server sent a certificate, although SecurityPolicy NONE is used
2016-09-30 14:55:33,525 INFO client.Subscription:? Invalid sequence number 7667 in availableSequenceNumbers list received from server. Current SequenceNumber=0
2016-09-30 14:55:33,526 INFO *disclosed* ServerState: CommunicationFault ==> Running
2016-09-30 14:55:39,450 INFO client.Subscription:? Invalid sequence number 7667 in availableSequenceNumbers list received from server. Current SequenceNumber=0
2016-09-30 14:55:39,577 INFO client.Subscription:? Invalid sequence number 7667 in availableSequenceNumbers list received from server. Current SequenceNumber=1


2016-09-30 16:12:16,116 INFO client.Subscription:? Invalid sequence number 7667 in availableSequenceNumbers list received from server. Current SequenceNumber=534
2016-09-30 16:12:16,217 INFO client.Subscription:? Invalid sequence number 7667 in availableSequenceNumbers list received from server. Current SequenceNumber=534
2016-09-30 16:12:16,317 INFO client.Subscription:? Invalid sequence number 7667 in availableSequenceNumbers list received from server. Current SequenceNumber=534
2016-09-30 16:12:16,418 INFO client.Subscription:? Invalid sequence number 7667 in availableSequenceNumbers list received from server. Current SequenceNumber=534
2016-09-30 16:12:16,518 INFO client.Subscription:? Invalid sequence number 7667 in availableSequenceNumbers list received from server. Current SequenceNumber=534
2016-09-30 16:12:16,618 INFO client.Subscription:? Invalid sequence number 7667 in availableSequenceNumbers list received from server. Current SequenceNumber=534

October 26, 2016
14:58, EEST
Avatar
MichaelBraveDigital
Member
Members
Forum Posts: 14
Member Since:
March 10, 2016
sp_UserOfflineSmall Offline

We are also running into this problem with the Client-Binary-2.2.2-638. The log files are getting spammed with this error multiple times per second:

10/26/2016 09:53:50.626 INFO [t@6579132e] bscription – Invalid sequence number 5133 in availableSequenceNumbers list received from server. Current SequenceNumber=4526
10/26/2016 09:53:50.726 INFO [t@6579132e] bscription – Invalid sequence number 4643 in availableSequenceNumbers list received from server. Current SequenceNumber=4526
10/26/2016 09:53:50.726 INFO [t@6579132e] bscription – Invalid sequence number 4644 in availableSequenceNumbers list received from server. Current SequenceNumber=4526
10/26/2016 09:53:50.726 INFO [t@6579132e] bscription – Invalid sequence number 5133 in availableSequenceNumbers list received from server. Current SequenceNumber=4526
10/26/2016 09:53:50.826 INFO [t@6579132e] bscription – Invalid sequence number 4643 in availableSequenceNumbers list received from server. Current SequenceNumber=4526
10/26/2016 09:53:50.826 INFO [t@6579132e] bscription – Invalid sequence number 4644 in availableSequenceNumbers list received from server. Current SequenceNumber=4526
10/26/2016 09:53:50.826 INFO [t@6579132e] bscription – Invalid sequence number 5133 in availableSequenceNumbers list received from server. Current SequenceNumber=4526
10/26/2016 09:53:50.926 INFO [t@6579132e] bscription – Invalid sequence number 4643 in availableSequenceNumbers list received from server. Current SequenceNumber=4526
10/26/2016 09:53:50.926 INFO [t@6579132e] bscription – Invalid sequence number 4644 in availableSequenceNumbers list received from server. Current SequenceNumber=4526
10/26/2016 09:53:50.926 INFO [t@6579132e] bscription – Invalid sequence number 5133 in availableSequenceNumbers list received from server. Current SequenceNumber=4526
10/26/2016 09:53:51.026 INFO [t@6579132e] bscription – Invalid sequence number 4643 in availableSequenceNumbers list received from server. Current SequenceNumber=4526
10/26/2016 09:53:51.026 INFO [t@6579132e] bscription – Invalid sequence number 4644 in availableSequenceNumbers list received from server. Current SequenceNumber=4526

I’m going to try updating to 2.2.4 to see if this is any better, but at this rate I’ll have to turn off subscription error logging.

October 26, 2016
15:24, EEST
Avatar
Jouni Aro
Moderator
Moderators
Forum Posts: 1026
Member Since:
December 21, 2011
sp_UserOfflineSmall Offline

Yes, this was fixed in 2.2.4. It’s only cosmetic, but still wrong…

Forum Timezone: Europe/Helsinki

Most Users Ever Online: 1919

Currently Online:
22 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: 731

Moderators: 7

Admins: 1

Forum Stats:

Groups: 3

Forums: 15

Topics: 1529

Posts: 6471

Newest Members:

PromotionToold, HypromeImpupe, toneylapham544, rondawolinski7, Marypof5711, roycedelargie91, kourtneyquisenbe, ellis87832073466, zkxwilliemae, gabriellabachus

Moderators: Jouni Aro: 1026, Pyry: 1, Petri: 0, Bjarne Boström: 1032, Jimmy Ni: 26, Matti Siponen: 349, Lusetti: 0

Administrators: admin: 1