Avatar

Please consider registering
guest

sp_LogInOut Log In sp_Registration Register

Register | Lost password?
sp_Search Search
Advanced Search
Advanced Search

— Forum Scope —




— Match —





— Forum Options —





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

sp_Search Search
Go to Bottom
No permission to create posts
sp_Feed Topic RSS sp_TopicIcon
Sequence number missmatch
September 29, 2016
12:45, EEST
Avatar
Izak
Member
Members
Forum Posts: 3
Member Since:
August 5, 2016
sp_UserOfflineSmall Offline
Go to Top
1sp_Permalink sp_Print

Hello!
We have a problem with an error “Sequence number missmatch”. Normally the communication is fine, then suddenly this happens and after that there are regular problems until the server side are restarted. Is this “Sequence number missmatch” something you are familiar with and know why it occur?

Client logs:

2016-09-27 11:08:44.063 ERROR [org.opcfoundation.ua.transport.tcp.io.TcpConnection] (TcpConnection/Read) localhost/127.0.0.1:49320 Sequence number mismatch
2016-09-27 11:08:44.065 ERROR [org.opcfoundation.ua.transport.tcp.io.SecureChannelTcp] (Blocking-Work-Executor-66165) 303255 Failed to renew security token.
org.opcfoundation.ua.common.ServiceResultException: Bad_UnexpectedError (code=0x80010000, description=”Sequence number mismatch”)
at org.opcfoundation.ua.transport.tcp.io.TcpConnection$ReadThread.run(Unknown Source)
2016-09-27 11:08:44.109 ERROR [org.opcfoundation.ua.transport.tcp.io.TcpConnection] (TcpConnection/Read) localhost/127.0.0.1:49320 Sequence number mismatch
2016-09-27 11:08:45.152 ERROR [org.opcfoundation.ua.transport.tcp.io.TcpConnection] (TcpConnection/Read) localhost/127.0.0.1:49320 Sequence number mismatch
2016-09-27 11:08:47.200 ERROR [org.opcfoundation.ua.transport.tcp.io.TcpConnection] (TcpConnection/Read) localhost/127.0.0.1:49320 Sequence number mismatch
2016-09-27 11:08:51.211 ERROR [org.opcfoundation.ua.transport.tcp.io.TcpConnection] (TcpConnection/Read) localhost/127.0.0.1:49320 Error
org.opcfoundation.ua.common.ServiceResultException: Bad_SecureChannelIdInvalid (0x80220000) “The specified secure channel is not longer valid.”
at org.opcfoundation.ua.transport.tcp.io.TcpConnection$ReadThread.run(Unknown Source)
2016-09-27 11:08:54.014 WARN (PublishTask-com.prosysopc.ua.client.UaClient@44a3b33b) Server state changed unexpectedly from “Running” to “CommunicationFault” in connection state “CONNECTED”.
2016-09-27 11:08:55.177 INFO [com.prosysopc.ua.client.UaClient] (PublishTask-com.prosysopc.ua.client.UaClient@44a3b33b) createSubscription: timeout subscription=2
2016-09-27 11:08:55.181 INFO [com.prosysopc.ua.client.UaClient] (PublishTask-com.prosysopc.ua.client.UaClient@44a3b33b) reconnect: Reconnected to server (session reactivated)
2016-09-27 11:08:55.183 WARN (PublishTask-com.prosysopc.ua.client.UaClient@44a3b33b) Server state changed unexpectedly from “CommunicationFault” to “Running” in connection state “CONNECTED”.

Server logs (Kepware):

9/27/2016 10:23:44 AM Information UA Server UaServer_EndpointCallback: SecureChannel 303255 renewed! [status=0x0]
9/27/2016 10:23:48 AM Information UA Server UaServer_EndpointCallback: SecureChannel 303253 renewed! [status=0x0]
9/27/2016 11:08:44 AM Information UA Server UaServer_EndpointCallback: SecureChannel 303254 renewed! [status=0x0]
9/27/2016 11:08:44 AM Information UA Server UaServer_EndpointCallback: SecureChannel 303255 renewed! [status=0x0]
9/27/2016 11:08:44 AM Information UA Server UaServer_EndpointCallback: SecureChannel 303255 renewed! [status=0x0]
9/27/2016 11:08:45 AM Information UA Server UaServer_EndpointCallback: SecureChannel 303255 renewed! [status=0x0]
9/27/2016 11:08:47 AM Information UA Server UaServer_EndpointCallback: SecureChannel 303255 renewed! [status=0x0]
9/27/2016 11:08:48 AM Information UA Server UaServer_EndpointCallback: SecureChannel 303253 renewed! [status=0x0]
9/27/2016 11:08:55 AM Information UA Server UaServer_EndpointCallback: SecureChannel 303256 opened!
9/27/2016 11:08:55 AM Information UA Server Security Mode 2 Security Policy http://opcfoundation.org/UA/SecurityPolicy#Basic128Rsa15
9/27/2016 11:09:01 AM Information UA Server UaServer_EndpointCallback: SecureChannel 0 closed! [status=0x80860000]
9/27/2016 11:09:01 AM Information UA Server UaServer_EndpointCallback: SecureChannel 0 closed! [status=0x80860000]
9/27/2016 11:09:01 AM Information UA Server UaServer_EndpointCallback: SecureChannel 0 closed! [status=0x80860000]
9/27/2016 11:53:44 AM Information UA Server UaServer_EndpointCallback: SecureChannel 303254 renewed! [status=0x0]
9/27/2016 11:53:48 AM Information UA Server UaServer_EndpointCallback: SecureChannel 303253 renewed! [status=0x0]
9/27/2016 11:53:55 AM Information UA Server UaServer_EndpointCallback: SecureChannel 303256 renewed! [status=0x0]
9/27/2016 12:12:34 PM Information UA Server UaServer_EndpointCallback: SecureChannel 303255 closed! [status=0x80860000]
9/27/2016 12:12:46 PM Information UA Server UaServer_EndpointCallback: SecureChannel 303257 opened!

October 4, 2016
13:29, EEST
Avatar
Heikki Tahvanainen
Moderator
Members

Moderators
Forum Posts: 402
Member Since:
April 17, 2013
sp_UserOfflineSmall Offline
Go to Top
2sp_Permalink sp_Print

Hello,

Sorry that the answering took such a long time. What SDK version are you using at the moment? Is this something that can be reproduced easily or is this problem occurring randomly?

Just to provide some more information, could you set the Stack logging level to WARN and provide the resulting log file about the situation? In the WARN level, the erroneous sequence numbers are logged.

This is not a known bug. Generally, this error message states that some message is missing. Initially it’s hard to say if this checking is practical or even sensible in the case of renewing secure channel.

October 6, 2016
16:23, EEST
Avatar
Izak
Member
Members
Forum Posts: 3
Member Since:
August 5, 2016
sp_UserOfflineSmall Offline
Go to Top
3sp_Permalink sp_Print

Hello,
Thanks for the feedback. We are using Prosys-OPC-UA-Java-SDK-Client-Binary-1.4.8-8731. This is nothing that can be reproduced easily, normally everything is fine for about a week until the problem do occur. I checked and it seems we already have the org.opcfoundation.ua set to WARN log level, so I am not sure why the sequence number were not logged when the problem occured. However, I will check again when the problem occur again.

October 6, 2016
16:43, EEST
Avatar
Heikki Tahvanainen
Moderator
Members

Moderators
Forum Posts: 402
Member Since:
April 17, 2013
sp_UserOfflineSmall Offline
Go to Top
4sp_Permalink sp_Print

Hi,

Thank you for the information. Could you try to test if the same issue is still reproduced with a newer SDK?

Currently version 2.2.4 is the latest release of the Java SDK: https://prosysopc.com/products/opc-ua-java-sdk/release-history/

No permission to create posts
sp_Feed All RSS
Go to top
Forum Timezone: Europe/Helsinki

Most Users Ever Online: 518

Currently Online:
11 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

hbrackel: 135

pramanj: 86

Francesco Zambon: 81

rocket science: 77

Ibrahim: 76

Sabari: 62

kapsl: 57

gjevremovic: 49

Xavier: 43

fred: 41

Member Stats:

Guest Posters: 0

Members: 683

Moderators: 16

Admins: 1

Forum Stats:

Groups: 3

Forums: 15

Topics: 1467

Posts: 6261

Newest Members:

digitechroshni, LouieWreve, Kickbiche, karrimacvitie5, graciela2073, sagarchau, elviralangwell4, Donnavek, Eddiefauth, DonaldPooma

Moderators: Jouni Aro: 1010, Otso Palonen: 32, Tuomas Hiltunen: 5, Pyry: 1, Petri: 0, Bjarne Boström: 983, Heikki Tahvanainen: 402, Jukka Asikainen: 1, moldzh08: 0, Jimmy Ni: 26, Teppo Uimonen: 21, Markus Johansson: 42, Niklas Nurminen: 0, Matti Siponen: 321, Lusetti: 0, Ari-Pekka Soikkeli: 5

Administrators: admin: 1