# Error when managing tag subscriptions

**URL:** <https://forum.inductiveautomation.com/t/error-when-managing-tag-subscriptions/29541>\
**Category:** Ignition\
**Created:** [October 30, 2019, 8:06pm UTC](https://forum.inductiveautomation.com/t/error-when-managing-tag-subscriptions/29541 "2019-10-30T20:06:50Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![gbclark](https://avatars.discourse-cdn.com/v4/letter/g/b487fb/32.png) [@gbclark](https://forum.inductiveautomation.com/u/gbclark)\
**Post date:** [October 30, 2019, 8:06pm UTC](https://forum.inductiveautomation.com/t/error-when-managing-tag-subscriptions/29541/1 "2019-10-30T20:06:50Z")

</div>

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)

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [October 30, 2019, 9:05pm UTC](https://forum.inductiveautomation.com/t/error-when-managing-tag-subscriptions/29541/2 "2019-10-30T21:05:42Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![catherine.fowler](https://avatars.discourse-cdn.com/v4/letter/c/34f0e0/32.png) [@catherine.fowler](https://forum.inductiveautomation.com/u/catherine.fowler)\
**Post date:** [September 3, 2024, 7:26pm UTC](https://forum.inductiveautomation.com/t/error-when-managing-tag-subscriptions/29541/4 "2024-09-03T19:26:13Z")

</div>

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

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/1/014b08b1cc1d1eb62f80d80ebd7c9def7ca32449.png)

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

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [September 3, 2024, 7:28pm UTC](https://forum.inductiveautomation.com/t/error-when-managing-tag-subscriptions/29541/5 "2024-09-03T19:28:30Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![catherine.fowler](https://avatars.discourse-cdn.com/v4/letter/c/34f0e0/32.png) [@catherine.fowler](https://forum.inductiveautomation.com/u/catherine.fowler)\
**Post date:** [September 3, 2024, 7:29pm UTC](https://forum.inductiveautomation.com/t/error-when-managing-tag-subscriptions/29541/6 "2024-09-03T19:29:41Z")

</div>

Ok thanks, will do.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [September 3, 2024, 7:31pm UTC](https://forum.inductiveautomation.com/t/error-when-managing-tag-subscriptions/29541/7 "2024-09-03T19:31:45Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![catherine.fowler](https://avatars.discourse-cdn.com/v4/letter/c/34f0e0/32.png) [@catherine.fowler](https://forum.inductiveautomation.com/u/catherine.fowler)\
**Post date:** [September 3, 2024, 7:52pm UTC](https://forum.inductiveautomation.com/t/error-when-managing-tag-subscriptions/29541/8 "2024-09-03T19:52:15Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Fadhil\_Semi](https://avatars.discourse-cdn.com/v4/letter/f/f19dbf/32.png) [@Fadhil\_Semi](https://forum.inductiveautomation.com/u/Fadhil_Semi)\
**Post date:** [May 21, 2026, 12:14pm UTC](https://forum.inductiveautomation.com/t/error-when-managing-tag-subscriptions/29541/9 "2026-05-21T12:14:25Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![catherine.fowler](https://avatars.discourse-cdn.com/v4/letter/c/34f0e0/32.png) [@catherine.fowler](https://forum.inductiveautomation.com/u/catherine.fowler)\
**Post date:** [May 25, 2026, 8:16pm UTC](https://forum.inductiveautomation.com/t/error-when-managing-tag-subscriptions/29541/10 "2026-05-25T20:16:51Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![mrosenkrans](https://avatars.discourse-cdn.com/v4/letter/m/bcef8e/32.png) [@mrosenkrans](https://forum.inductiveautomation.com/u/mrosenkrans)\
**Post date:** [June 8, 2026, 8:35pm UTC](https://forum.inductiveautomation.com/t/error-when-managing-tag-subscriptions/29541/11 "2026-06-08T20:35:50Z")

</div>

@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.
