Hello,

We have been observing intermittent subscription timeouts with our Prosys Java OPC Client (v4.02) and as a workaround, have implemented a restart protocol to re-establish connectivity to Kepware.

This works as expected, but in certain situations following the reconnect attempt, we get the following error:

SecureChannelTcp – -1095008988: Error recovery = true
TcpConnection – /xxx.xxx.xxx.xxx:49320 Connecting
TcpConnection – Connected (non-reverse), handshake completed, local=/10.35.105.11:51594, remote=/xxx.xxx.xxx.xxx:49320
TcpConnection – /xxx.xxx.xxx.xxx:49320 Error
Bad_RequestTypeInvalid (code=0x80530000, description=”The security token request type is not valid.”)
at com.prosysopc.ua.stack.transport.tcp.io.TcpConnection$b.run(SourceFile:276)
TcpConnection – /xxx.xxx.xxx.xxx:49320 Closed
SecureChannelTcp – -1095008988: Error recovery = false
OpcUaClientSession$ – ServiceException subscribing to tag `opc.tcp://xxx.xxx.xxx.xxx:49320/ns=2;s=M364_Z4.M364_Z4.Packout.300R1MH.Count`
com.prosysopc.ua.ServiceException: Bad_RequestTypeInvalid (code=0x80530000, description=”The security token request type is not valid.”) ServiceResult=Bad_RequestTypeInvalid (0x80530000) “The security token request type is not valid.”

At this point, the connection requires a full restart of the client.

Looking online, I’ve found something similar with Ignition’s OPC client and bad responses from Kepware as well:

https://forum.inductiveautomation.com/t/opc-connection-fail-from-opc-tag-browser-to-designer/17674/6

Is there anything that can be called explicitly in the Prosys client stack to ensure this restart is clean?

Thank you!