

19:22, EEST

June 8, 2016

We are using:
OPC UA Client:
Prosys-OPC-UA-Java-SDK-Client-Binary-2.3.0-764.jar
Opc.Ua.Stack-1.02.337.12.jar
OPC UA Server:
prosys-opc-ua-simulation-server-windows-x64-5.0.2-242.exe
We are calling getNode() (well, or getType()) on i=47 (which happens to be ReferenceType “HasComponent”) and then we get this:
Exception in thread “TcpConnection/Read” java.lang.IllegalArgumentException: Value underflow
at org.opcfoundation.ua.builtintypes.UnsignedInteger.(Unknown Source)
at org.opcfoundation.ua.encoding.binary.BinaryDecoder.getExpandedNodeId(Unknown Source)
at org.opcfoundation.ua.core.EncodeableSerializer$81.getEncodeable(Unknown Source)
at org.opcfoundation.ua.encoding.utils.AbstractSerializer.getEncodeable(Unknown Source)
at org.opcfoundation.ua.encoding.utils.SerializerComposition.getEncodeable(Unknown Source)
at org.opcfoundation.ua.encoding.binary.BinaryDecoder.getEncodeableArray(Unknown Source)
at org.opcfoundation.ua.core.EncodeableSerializer$82.getEncodeable(Unknown Source)
at org.opcfoundation.ua.encoding.utils.AbstractSerializer.getEncodeable(Unknown Source)
at org.opcfoundation.ua.encoding.utils.SerializerComposition.getEncodeable(Unknown Source)
at org.opcfoundation.ua.encoding.binary.BinaryDecoder.getEncodeableArray(Unknown Source)
at org.opcfoundation.ua.core.EncodeableSerializer$84.getEncodeable(Unknown Source)
at org.opcfoundation.ua.encoding.utils.AbstractSerializer.getEncodeable(Unknown Source)
at org.opcfoundation.ua.encoding.utils.SerializerComposition.getEncodeable(Unknown Source)
at org.opcfoundation.ua.encoding.binary.BinaryDecoder.getMessage(Unknown Source)
at org.opcfoundation.ua.transport.tcp.io.TcpConnection$ReadThread.run(Unknown Source)
And in the following, the actual calling thread runs into this:
com.prosysopc.ua.ServiceException: Bad_Timeout (code=0x800A0000, description=”The operation timed out.”)
at com.prosysopc.ua.client.UaClient.doRead(Unknown Source) ~[prosys-opc-ua-client-2.3.0-764.jar:2.3.0.764]
at com.prosysopc.ua.client.UaClient.read(Unknown Source) ~[prosys-opc-ua-client-2.3.0-764.jar:2.3.0.764]
at com.prosysopc.ua.client.UaClient.readAttributes(Unknown Source) ~[prosys-opc-ua-client-2.3.0-764.jar:2.3.0.764]
at com.prosysopc.ua.client.UaClient.readAttributes(Unknown Source) ~[prosys-opc-ua-client-2.3.0-764.jar:2.3.0.764]
at com.prosysopc.ua.client.AddressSpace.getNode(Unknown Source) ~[prosys-opc-ua-client-2.3.0-764.jar:2.3.0.764]
at com.prosysopc.ua.client.AddressSpace.getType(Unknown Source) ~[prosys-opc-ua-client-2.3.0-764.jar:2.3.0.764]
Any explanation on this? Known Bug in Client? (see Version above), Update opc-ua-stack? From where?
THANK YOU!
13:05, EEST

Moderators
February 11, 2020

Hello,
This is a known issue that has been fixed in version 3.1.6 of the Prosys OPC UA SDK for Java. See https://github.com/OPCFoundati…..issues/155 for more information on the underlying issue and https://downloads.prosysopc.co…..sion-3-1-6 for the release notes for version 3.1.6.
Please update to either version 3.1.6 or a newer version of the SDK. We would recommend you to update to version 4.x of the SDK, if that is possible for you.
1 Guest(s)
