Re: [milo-dev] Possible cause of Bad_TcpMessageTooLarge

[Kevin Herron <kevinherron@xxxxxxxxx>]

Thomas,

I took a look and the only place that error message is used is in ChunkDecoder, which means it's definitely from a message from the server that is too large. Are you in a position where you could get a Wireshark capture so we can see what kind of response it is? I'd like to know exactly what is happening before I suggest workarounds for this.

On Mon, Nov 2, 2020 at 6:02 AM Kevin Herron <kevinherron@xxxxxxxxx> wrote:

Thomas,

Can you post the full stack trace of that error message?

It means either client or server is trying to send a message that exceeds that max size negotiated by the connection. Since you already chunked up your monitored item creation I’m not sure what other large message you could be sending, so it may be the server trying to send a very large response. The full stack trace may help figure out which it is.

On Nov 2, 2020, at 02:42, Edhag Thomas <Thomas.Edhag@xxxxxxx> wrote:



Hi!

  I'm using the ManagedSubscription API to set up about 50000 monitored items. The creation of monitored items are chunked up in smaller sublists of NodeID before looping through creation. The subscription is done against a NodeOpcUa.

...in the loop of sublists my code looks like:

subscription.createDataItems(sublist, (item)->{

    if (item.getStatusCode().isGood()) {
        item.addDataValueListener((value)->{
            //Do something with item and value
        });
    }

});

So even if I don't do anything with the monitored item in the callback,

after a while (upto 1h) I get a UaException: status=Bad_TcpMessageTooLarge, message=message size exceeds configured limit: 3789570 > 2097152?




What is the most probable cause of this error?




,regards

Thomas


_______________________________________________
milo-dev mailing list
milo-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/milo-dev