Hi,
I can do that, but it seems that the problem occurs only when I call
client.getAddressSpace().browseNodes(parentNodeId);
At that point the client doesn’t have anything else going on, this is done just after
connection has been opened. So there is no subscription yet.
The server is a very large one, I think that there are thousands of tags.
(Browsing with UaExpert works, but is slow due to amount of tags).
Ari S.
Can you turn the logger for org.eclipse.milo.opcua.sdk.client.subscriptions.OpcUaSubscriptionManager to DEBUG level and then tell me if you get any messages about "Publish service failure"? Or do you have any other timeout messages that
occur during or soon after this decoding error?
You can probably work around by increasing encoding limits but I'd like to narrow it down a little bit. If it's the occasional PublishResponse that is too large then decreasing the"maxNotificationsPerPublish" parameter when creating a subscription
may help.
Hi,
Any workarounds what I could try on my own code if I cannot get capture ?
OpcUaClientConfigBuilder.setEncodingLimits() ?
Ari S.
Maybe if the server allows MessageSecurityMode.sign, but not it it’s only SignAndEncrypt.
Hi,
The server requires encryption on. Would wireshark capture still be interesting ?
Ari S.
It looks like the server is responding with a message that is larger than the agreed upon max message size / max chunk count.
While I think this is ultimately a server issue, if you can get a Wireshark capture then perhaps we can see what kind of Response this is and what Request from the client is provoking
this issue.
Hi,
I’m working with connection to ABB’s RTDB OPC UA server (version 5.0). Otherwise things seem to be working just fine, except
when trying to browse for tags things break like this:
2022-02-03 12:12:25.933 [milo-netty-event-loop-5] ERROR [remote=IMPI3/10.16.16.41:4841]
Exception caught: UaException: status=Bad_TcpMessageTooLarge, message=max chunk count exceeded (64)io.netty.handler.codec.DecoderException: UaException: status=Bad_TcpMessageTooLarge, message=max chunk count exceeded (64) at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:471)
at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:276) at io.netty.handler.codec.ByteToMessageCodec.channelRead(ByteToMessageCodec.java:103) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166) at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:719) at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:655)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:581) at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493) at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at java.base/java.lang.Thread.run(Thread.java:829)Caused by: org.eclipse.milo.opcua.stack.core.UaException: max chunk count exceeded (64) at org.eclipse.milo.opcua.stack.client.transport.uasc.UascClientMessageHandler.accumulateChunk(UascClientMessageHandler.java:426)
at org.eclipse.milo.opcua.stack.client.transport.uasc.UascClientMessageHandler.onSecureMessage(UascClientMessageHandler.java:608) at org.eclipse.milo.opcua.stack.client.transport.uasc.UascClientMessageHandler.decodeMessage(UascClientMessageHandler.java:399)
at org.eclipse.milo.opcua.stack.client.transport.uasc.UascClientMessageHandler.decode(UascClientMessageHandler.java:383) at io.netty.handler.codec.ByteToMessageCodec$1.decode(ByteToMessageCodec.java:42) at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:501)
at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:440) ... 17 common frames omitted
I wonder what I should do to fix this ? Or is this some kind of problem at server side ?
Ari S.
_______________________________________________
milo-dev mailing list
milo-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/milo-dev
_______________________________________________
milo-dev mailing list
milo-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/milo-dev
_______________________________________________
milo-dev mailing list
milo-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/milo-dev