Error when managing tag subscriptions

Ignition
1

We are getting this error logged frequently in the Gateway log. Ignition 8.0.2

Detail is:
java.lang.NullPointerException: null

at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.ext.AbstractPropertySetNode.uninstall(AbstractPropertySetNode.java:84)

at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.ext.AbstractPropertySetNode$PropertyNode.shutdown(AbstractPropertySetNode.java:131)

at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.ext.AbstractGeneratingTagNode.setSubscription(AbstractGeneratingTagNode.java:40)

at com.inductiveautomation.ignition.gateway.tags.subscriptions.ProviderSubscriptionManagerImpl$SubscriptionNode$PropertySubscription.shutdown(ProviderSubscriptionManagerImpl.java:656)

at com.inductiveautomation.ignition.gateway.tags.subscriptions.ProviderSubscriptionManagerImpl$SubscriptionNode$PropertySubscription.removeListener(ProviderSubscriptionManagerImpl.java:640)

at com.inductiveautomation.ignition.gateway.tags.subscriptions.ProviderSubscriptionManagerImpl$SubscriptionNode$LeasingPropertySubscription.removeListener(ProviderSubscriptionManagerImpl.java:719)

at com.inductiveautomation.ignition.gateway.tags.subscriptions.ProviderSubscriptionManagerImpl$SubscriptionNode.removeListener(ProviderSubscriptionManagerImpl.java:364)

at com.inductiveautomation.ignition.gateway.tags.subscriptions.ProviderSubscriptionManagerImpl.manage(ProviderSubscriptionManagerImpl.java:181)

at com.inductiveautomation.ignition.gateway.tags.subscriptions.ProviderSubscriptionManagerImpl.lambda$subscriptionChanged$2(ProviderSubscriptionManagerImpl.java:148)

at java.base/java.util.ArrayList.forEach(Unknown Source)

at java.base/java.util.Collections$UnmodifiableCollection.forEach(Unknown Source)

at com.inductiveautomation.ignition.gateway.tags.subscriptions.ProviderSubscriptionManagerImpl.subscriptionChanged(ProviderSubscriptionManagerImpl.java:148)

at com.inductiveautomation.ignition.gateway.tags.model.TagSubscriptionModel$ChangeNotificationJob.run(TagSubscriptionModel.java:266)

at com.inductiveautomation.ignition.common.execution.impl.BasicExecutionEngine$ThrowableCatchingRunnable.run(BasicExecutionEngine.java:518)

at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

at java.base/java.util.concurrent.FutureTask.run(Unknown Source)

at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)

at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

2

Update your gateway, this is a bug that’s resolved in subsequent versions.

4

I have the same frequent error on my gateway, but with fewer details logged:

image
image1179×176 8.97 KB

My gateway version is 8.1.36 though. Has the bug been reintroduced, or is there another cause...?

5

Hmm, could be a different/new bug, this seems to be a catch-all handler / log message. Best to contact support so they can help figure out what's causing it.

6

Ok thanks, will do.

7

You sure it's 8.1.36? I would have expected a more detailed NullPointerException / stack trace from JDK 17 :confused:

8

Certain. It also stood out to me as weird for that reason.

9

Im running into the same problem with v8.1.39 - any updates on the fix mate?

10

Unfortunately, no. I made a support ticket, the support staff got a backup of the gateway, and then I heard nothing more. Wasn't causing functional issues, so I left it alone.

@maggie_castro94 , I think you are the support rep who took the ticket over (apologies if you're not); was there ever any headway made?

11

@catherine.fowler as it pertains to your specific ticket, I was not able to replicate the error so no further progress was made beyond what had been discussed with the previous Support Engineer on the ticket.

@Fadhil_Semi I advise opening a support ticket to troubleshoot the error.

These NullPointerException errors should be investigated but a full stack trace should be supplied to aid in troubleshooting. If no full stack trace is available then additional debug logging may be needed to capture the full stack trace. Support should be able to provide guidance on the best approach for capturing more details.