-
-
Notifications
You must be signed in to change notification settings - Fork 480
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[NODE-OPCUA-E11] message size 16385 exceeds the negotiated message size 16384 nb chunks 1. #1335
Comments
Please forward this request to nodered-contrib-opcua forum, if you need a community answer. Alternatively, we encourage you to use |
Why you just rename my Issue like that? I am using
And this seems to be a bug in your node-opcua lib. The servers maxMessageSize is 16384, which is negotiated with the client. |
It was mentioned the issue was similar to #1263, which relates to node-red-contrib-opcua. Hence the confusion. Sorry for this. Please adjust this initial issue description by filling carefully the Bug reporting template , providing clear step by step instructions to reproduce, version of node-opcua involved, describing the third party OPC Server you're trying to connect to: ( manufacturer, version) etc .... |
--> Current behavior I have an OPC UA Client created with the node-opcua library. The connection to other OPC UA servers generally works. This is evidence that an OPC UA client-server connection with the labeling system generally works. Describe the bug First, I have enabled the following for an extended debug output. process.env.NODEOPCUADEBUG = "TRANSPORT{HELACK-CHUNK}"; Then I used this connection routine. this.client = opcua.OPCUAClient.create({
endpointMustExist: true, // also tried false and different transportSettings{...}
}); I received the following outputs. ´´´ Subsequently, no connection is established. As I understand it, the client and server agree on the server's maxMessageSize of 16384 bytes. However, the client violates this agreement by sending a message with 16385 bytes (one byte more than agreed upon). Step by step instruction to reproduce Actually i followed the advice: Steps to reproduce the behavior:
process.env.NODEOPCUADEBUG = "TRANSPORT{HELACK-CHUNK}";
this.client = opcua.OPCUAClient.create({
endpointMustExist: true, // also tried false and different transportSettings{...}
});
Expected behavior In the positive case, I would expect a successful connection setup from the client to the server. Screenshots Gist process.env.NODEOPCUADEBUG = "TRANSPORT{HELACK-CHUNK}";
const { OPCUAClient } = require("node-opcua");
// replace this line with the targeted server endpoint URL:
const endpointUrl = "opc.tcp://...";
(async () => {
const client = OPCUAClient.create({});
await client.connect(endpointUrl);
await client.disconnect();
})(); Context
|
can you provide description of the other OPCUA system you are trying to connect to: Name: __ This is where it gets interesting to be able to reproduce.
|
The other OPCUA system I am trying to connect to: Name: Alpha HSM (https://www.bluhmsysteme.com/etikettierung/etikettenspender/alpha-hsm.html) So you want to buy this system to reproduce the problem? I think the Debug log of the connection process that i provided is the most important information. |
I should be able to investigate without .... stay tuned |
fixed in node-opcua@2.200.0 |
Thanks a lot, i tested it and it works now! |
Problem:
I cannot establish connection to a certain OPC UA Server with my OPC UA Client. (Connections to other tested OPC UA Servers do work)
I have a similar Issue like #1263 which is already closed. But the replys there, which i tested could not help me. In my case there seems to be a mismatch of 1 Byte only:
[NODE-OPCUA-E11] message size 16385 exceeds the negotiated message size 16384 nb chunks 1
Details (process.env.NODEOPCUADEBUG = "TRANSPORT{HELACK-CHUNK}";):
10:17:38.521Z :client_tcp_transport :285 sending Hello
... protocolVersion = 0
... receiveBufferSize = 655360
... sendBufferSize = 655360
... maxMessageSize = 0
... maxChunkCount = 0
... endpointUrl = opc.tcp://172.18.4.25:48020
...
10:17:38.523Z :client_tcp_transport :263 receiving Ack
... protocolVersion = 0
... receiveBufferSize = 16384
... sendBufferSize = 16384
... maxMessageSize = 16384
... maxChunkCount = 1
...
10:17:38:524 MESSAGE BUILDER LIMITS maxMessageSize = 16384 maxChunkCount = 1 maxChunkSize = 16384 ( 16384 )
10:17:38.527Z :message_chunker :117 [NODE-OPCUA-E11] message size 16385 exceeds the negotiated message size 16384 nb chunks 1
The text was updated successfully, but these errors were encountered: