Ignition to Martikon OPC UA Tunneler Faulted connection error

We are using Ignition edge to connect to an OEM 's system that is using Martikon Tunneler to provide OPC UA data.

The connection is configured and shows as connecting and allows us to use Ignition Designer to browse and select OPC UA tags to add and collect values from.

We are seeing on repeated occasions across multiple deployments that the OPC connection becomes Faulted and we can no longer connect to the Matrikon tunneler.

The error given on Ignition is as below

java.lang.Exception: session inactive: id=NodeId{ns=4, id=723486665} name=ignition[Ignition-SPR]_Honeywell_1720550181072
	at com.inductiveautomation.ignition.gateway.opcua.client.connection.OpcUaConnection$MiloSessionActivityListener.onSessionInactive(OpcUaConnection.kt:498)
	at org.eclipse.milo.opcua.sdk.client.session.SessionFsmFactory.lambda$null$39(SessionFsmFactory.java:577)
	at java.base/java.util.concurrent.CopyOnWriteArrayList.forEach(Unknown Source)
	at org.eclipse.milo.opcua.sdk.client.session.SessionFsmFactory.lambda$configureActiveState$40(SessionFsmFactory.java:577)
	at com.digitalpetri.strictmachine.dsl.ActionBuilder$PredicatedTransitionAction.execute(ActionBuilder.java:119)
	at com.digitalpetri.strictmachine.StrictMachine$PollAndEvaluate.lambda$run$0(StrictMachine.java:242)
	at java.base/java.util.ArrayList.forEach(Unknown Source)
	at com.digitalpetri.strictmachine.StrictMachine$PollAndEvaluate.run(StrictMachine.java:227)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)

8.1.17 (b2022051210)
Azul Systems, Inc. 11.0.15

The OEM is struggling to see any issue on their side, has anyone seen similar activity before? Is there a setting we need to change on the Ignition side of the connection that might help?

Can you share the Ignition logs?

This error you've shared is just the stack trace that happens when you lose the connection to the server for some reason. It doesn't help narrow down why that happened.


Log file is attached, hope this is what you were after.

Ignition-SPR-Groov_Ignition_logs_20240710-1709.zip|attachment](upload://gDSNdwXkWfMUZJyCwLOtldS3OgK.zip) (3.1 MB)

Looks like it might have been had it uploaded correctly.

Try again, if it doesn't work I can send you a dropbox link if you don't have anywhere to upload them.

Yes, I had a suspicion it did not work. Trying again.

Ignition-SPR-Groov_Ignition_logs_20240710-1709.zip (3.1 MB)

It looks like occasionally the server stops responding to the Ignition client "keep alive" request that reads the server's current time and state variables. In the settings for the connection to this server you can try increasing the number of keep alive failures allowed and/or the keep alive timeout to give the server longer to respond.

Thanks, are there any recommended settings for settings? Am I correct in thinking changing the "Keep-Alive Failures Allowed" to 0 will mean Ignition will never set the connection to faulted even if the keep alive continually fail?

We have another deployment with a similar issue, would you be able to check this log to see if its the same issue? Appreciate your assistance.

Ignition-ACR-Groov_Ignition_logs_20240711-1455.zip (5.3 MB)

No, best set it to 9999999 or something if you want that behavior.

Looks like the same set of errors.

Matrikon [tunneler] is notoriously... not good.

Thanks for checking, yes I am learning the hard way that Matrikon is not so good but unfortunately that's all the OEM will provide.

We think the issues is with the Matrikon failing, but they keep pointing at Ignition.

Thanks for all your help, we will increase the Keep Alive failures and the Keep Alive timeout and see how we go.