Opc connection FAULTED with exception session inactive

Ignition
1

Ignition 8.3.9

We connect to an opcua server for Video-based Automatic Incident Detection with a virtual IP Address.

Sometime we are disconnected, Ignition connection is FAULTED with the following error:

java.lang.Exception: session inactive: id=NodeId{ns=1, id=a7d319ac-7438-4f41-ac42-b9171f85ffa7} name=ignition_1793954736501
	at com.inductiveautomation.ignition.gateway.opcua.client.connection.OpcUaConnection$MiloSessionActivityListener.onSessionInactive(OpcUaConnection.kt:460)
	at org.eclipse.milo.opcua.sdk.client.session.SessionFsmFactory.lambda$configureActiveState$42(SessionFsmFactory.java:737)
	at java.base/java.util.concurrent.CopyOnWriteArrayList.forEach(Unknown Source)
	at org.eclipse.milo.opcua.sdk.client.session.SessionFsmFactory.lambda$configureActiveState$43(SessionFsmFactory.java:736)
	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)

We have to disable/enable the connection to reconnect.

We suspect the opcua server is non-transparent for the opcua client and we need to reconnect each time the virtual address switch.

@Kevin.Herron is the Exception normal for this use case ?

Can we force the connection to reconnect ?

2

Hi Lionel,

We ran into a similar session inactive issue for a while until we upgraded to 8.3.10. This could be an unrelated problem but upgrading might be worth considering.

3

The session inactive error is just a generic "we lost the connection" kind of error. Cause could be anything.

That it won't automatically reconnect might be solved by an issue fixed in 8.3.10. If it still won't reconnect after that, we'll need logs / thread dump / Wireshark.

4

Thanks we will try to upgrade to 8.910 (or 8.9.11) as soon as possible to see if it solve this issue.