Log In
Register
Forum
Topic RSS
2:11, EET
March 22, 2024
Offline
I have server running but I can see this Info level logs
2024-03-21T17:22:26.541-06:00 INFO 541496 — [ork-Executor-25] com.prosysopc.ua.server.Subscription : Acknowledge on Subscription 1: 1 – Bad_SequenceNumberUnknown
2024-03-21T17:22:26.542-06:00 INFO 541496 — [ork-Executor-25] com.prosysopc.ua.server.Subscription : Acknowledge on Subscription 1: 1 – Bad_SequenceNumberUnknown
2024-03-21T17:22:26.542-06:00 INFO 541496 — [ork-Executor-25] com.prosysopc.ua.server.Subscription : Acknowledge on Subscription 1: 2 – Bad_SequenceNumberUnknown
What does that mean? Is there something wrong with it and how can I fix it?
10:54, EET
April 3, 2012
Offline
Hi,
What version of the SDK you are using?
Is the client made with our SDK?
The server side logs this when it will send Bad_SequenceNumberUnknown to a client. Will happen when client sends that sequenceNumber in PublishResponses acknowledging that it has received it and the server side doesn’t recognize it. By default server side does hold 10 newest notification sequence number’s related data in the client needs to RePublish(Request) the info if it for some reason has missed them. But if you do send notifications fast enough and the client would be slow enough it could also be just that the buffer no longer has the message.
20:30, EET
March 22, 2024
Offline
Hi,
I use 4.5.4-1405
I’m using kepserver opc client.
So the sequence number originated from the server but when the client acknowledges it the server doesn’t recognize it? Would increasing the default help? In case there is more than 10 in the queue the oldest one I guess will be removed and hence not recognized anymore? (I do send a lot of data so it might be the case). If so what is the property to set? and is there any drawbacks to that?
Thanks
9:03, EET
April 3, 2012
Offline
You would increase the queue size with:
server.getSubscriptionManager().setMaxRetransmissionQueueSize(100)
(Each Subscription has their own queue)
Notifications are kept in the queue until the client acknowledges them (or oldest removed if at limit), so if the size is increased it will take up potentially more memory depending how fast the client will acknowledge them. But as long as there is enough of memory there shouldn’t be any downsides.
Alternatively I guess it could also be just a client issue in general. Probably not server-side, though a note that the SDK 4.5.4 is about 3 years old at this point and has gotten fixes over the years, though I do not remember any related to this. Latest is 5.1.0.
https://downloads.prosysopc.com/opcua/Prosys_OPC_UA_SDK_for_Java_4_Release_Notes.html
https://downloads.prosysopc.com/opcua/Prosys_OPC_UA_SDK_for_Java_5_Release_Notes.html
But your client might also be as old, so I would recommend checking it’s version and release notes if the above didn’t help.
Most Users Ever Online: 1919
Currently Online:
60 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: 734
Moderators: 7
Admins: 1
Forum Stats:
Groups: 3
Forums: 15
Topics: 1523
Posts: 6449
Newest Members:
christamcdowall, redaahern07571, nigelbdhmp, travistimmons, AnnelCib, dalenegettinger, howardkennerley, Thomassnism, biancacraft16, edgardo3518Moderators: Jouni Aro: 1026, Pyry: 1, Petri: 0, Bjarne Boström: 1026, Jimmy Ni: 26, Matti Siponen: 346, Lusetti: 0
Administrators: admin: 1
