# \[BUG-6826\]: Change notification error flooding the log after updating to 8.1.22

**URL:** <https://forum.inductiveautomation.com/t/bug-6826-change-notification-error-flooding-the-log-after-updating-to-8-1-22/66541>\
**Category:** Ignition\
**Created:** [November 15, 2022, 7:03pm UTC](https://forum.inductiveautomation.com/t/bug-6826-change-notification-error-flooding-the-log-after-updating-to-8-1-22/66541 "2022-11-15T19:03:34Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![justin.huggins](https://avatars.discourse-cdn.com/v4/letter/j/d07c76/32.png) [@justin.huggins](https://forum.inductiveautomation.com/u/justin.huggins)\
**Post date:** [November 15, 2022, 7:03pm UTC](https://forum.inductiveautomation.com/t/bug-6826-change-notification-error-flooding-the-log-after-updating-to-8-1-22/66541/1 "2022-11-15T19:03:34Z")

</div>

I am testing out 8.1.22 and just upgraded from 8.1.17. After upgrading, our log is just being flooded with change notification error (tags.execution.batch.changeNotification). The basic error just says "java.lang.NullPointerException: null' on every entry. I switched to debug and it appears to not even actually change to debug mode. The little icon still has the red error icon even when switching 'tags.execution.batch.changeNotification' to debug as shown in the image. Any suggestions ideas before elevating to support? This is in our dev environment, but really would like to capture the memory leak error fixed in 8.1.22 in our prod environment soon.

 ![batchnotificationError](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/a/6a87afa6bead3fc3aaaccc0230202eb26b6bc00a.png)

---

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [November 15, 2022, 7:32pm UTC](https://forum.inductiveautomation.com/t/bug-6826-change-notification-error-flooding-the-log-after-updating-to-8-1-22/66541/2 "2022-11-15T19:32:12Z")

</div>

We have this issue as well but in 8.1.21, and need to upgrade to 22 for the remote provider memory leak as well

---

<div class="post-metadata">

**Author:** ![ggross](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ggross/32/12668_2.png) [@ggross](https://forum.inductiveautomation.com/u/ggross)\
**Post date:** [November 15, 2022, 7:42pm UTC](https://forum.inductiveautomation.com/t/bug-6826-change-notification-error-flooding-the-log-after-updating-to-8-1-22/66541/3 "2022-11-15T19:42:56Z")

</div>

Would it be possible to expand the error message so we can see a stack trace?

Thanks,  
Garth

---

<div class="post-metadata">

**Author:** ![justin.huggins](https://avatars.discourse-cdn.com/v4/letter/j/d07c76/32.png) [@justin.huggins](https://forum.inductiveautomation.com/u/justin.huggins)\
**Post date:** [November 15, 2022, 8:14pm UTC](https://forum.inductiveautomation.com/t/bug-6826-change-notification-error-flooding-the-log-after-updating-to-8-1-22/66541/4 "2022-11-15T20:14:25Z")

</div>

> [@justin.huggins](#):
>
> java.lang.NullPointerException: null is what shows up on everyone of them.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/5/f50413239c604c30c549e28ac1773ad29b08c98f.png)

---

<div class="post-metadata">

**Author:** ![justin.huggins](https://avatars.discourse-cdn.com/v4/letter/j/d07c76/32.png) [@justin.huggins](https://forum.inductiveautomation.com/u/justin.huggins)\
**Post date:** [November 15, 2022, 8:15pm UTC](https://forum.inductiveautomation.com/t/bug-6826-change-notification-error-flooding-the-log-after-updating-to-8-1-22/66541/5 "2022-11-15T20:15:49Z")

</div>

Same here, we just added another backend gateway for a new acquisition and are having to restart the gateway once a week as a band-aid.

---

<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:** [November 15, 2022, 8:16pm UTC](https://forum.inductiveautomation.com/t/bug-6826-change-notification-error-flooding-the-log-after-updating-to-8-1-22/66541/6 "2022-11-15T20:16:11Z")

</div>

> [@justin.huggins](#):
>
> java.lang.NullPointerException: null is what shows up on everyone of them.

_cries in JDK 11_

---

<div class="post-metadata">

**Author:** ![ggross](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ggross/32/12668_2.png) [@ggross](https://forum.inductiveautomation.com/u/ggross)\
**Post date:** [November 15, 2022, 8:32pm UTC](https://forum.inductiveautomation.com/t/bug-6826-change-notification-error-flooding-the-log-after-updating-to-8-1-22/66541/7 "2022-11-15T20:32:57Z")

</div>

> [@justin.huggins](#):
>
> java.lang.NullPointerException: null is what shows up on everyone of them.

If this is a test environment, any chance you can add the following line to your `data/ignition.conf` file under the `# Java Additional Parameters` heading (updating the number 6 if necessary)?

```auto
wrapper.java.additional.6=-XX:-OmitStackTraceInFastThrow

```

On restart, in theory, it should start providing a stack trace.

Thanks,  
Garth

---

<div class="post-metadata">

**Author:** ![ggross](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ggross/32/12668_2.png) [@ggross](https://forum.inductiveautomation.com/u/ggross)\
**Post date:** [November 17, 2022, 9:49pm UTC](https://forum.inductiveautomation.com/t/bug-6826-change-notification-error-flooding-the-log-after-updating-to-8-1-22/66541/8 "2022-11-17T21:49:17Z")

</div>

@nminchin or @justin.huggins, we haven't been able to replicate this internally so any additional information you could provide would be beneficial. Ideally adding the item noted above to the `ignition.conf` file would be great as it should throw a full error. It isn't something that should impact a running system other than a restart of the Gateway is required for it to take effect (hence the reason I brought up the fact it was a test system).

If that can't be done, if you could make a copy of a Gateway backup available and send me information via a direct message on how to access it would be something that we could also work with.

A call to support would also work if you are so inclined. At this point, we have no reports of this issue that I can find and would like to figure out a solution.

Thanks,  
Garth

---

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [November 17, 2022, 9:52pm UTC](https://forum.inductiveautomation.com/t/bug-6826-change-notification-error-flooding-the-log-after-updating-to-8-1-22/66541/9 "2022-11-17T21:52:40Z")

</div>

> [@ggross](#):
>
> Ideally adding the item noted above to the `ignition.conf` file would be great as it should throw a full error

Can do, on it now. Also, coincidentally, I have a 1600s flight recording on startup which I forgot I enabled, if that would help?

I might reduce it to 300s... 1600 might be MASSIVE

---

<div class="post-metadata">

**Author:** ![ggross](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ggross/32/12668_2.png) [@ggross](https://forum.inductiveautomation.com/u/ggross)\
**Post date:** [November 17, 2022, 9:56pm UTC](https://forum.inductiveautomation.com/t/bug-6826-change-notification-error-flooding-the-log-after-updating-to-8-1-22/66541/10 "2022-11-17T21:56:37Z")

</div>

> [@nminchin](#):
>
> Also, coincidentally, I have a 1600s flight recording on startup which I forgot I enabled, if that would help?

I'll take it. It will give us insight into what is running. As we are flying blind with this, not sure if it will help at all but it can't hurt.

---

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [November 17, 2022, 9:59pm UTC](https://forum.inductiveautomation.com/t/bug-6826-change-notification-error-flooding-the-log-after-updating-to-8-1-22/66541/11 "2022-11-17T21:59:29Z")

</div>

Here's the new log (seems a lot more useful!):

```auto
java.lang.NullPointerException: null

at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.complex.UdtTypeDefinitionNode.getInvalidTypeBrowseValue(UdtTypeDefinitionNode.java:155)

at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.complex.AbstractComplexTagNode.getDisplayValue(AbstractComplexTagNode.java:143)

at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.BasicTagDefinition.getBrowseInfo(BasicTagDefinition.java:374)

at com.inductiveautomation.ignition.gateway.tags.config.BatchStructureChangeOperation.lambda$createTagStructureEvent$0(BatchStructureChangeOperation.java:64)

at java.base/java.util.stream.ReferencePipeline$3$1.accept(Unknown Source)

at java.base/java.util.LinkedList$LLSpliterator.forEachRemaining(Unknown Source)

at java.base/java.util.stream.AbstractPipeline.copyInto(Unknown Source)

at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(Unknown Source)

at java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(Unknown Source)

at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(Unknown Source)

at java.base/java.util.stream.AbstractPipeline.evaluate(Unknown Source)

at java.base/java.util.stream.ReferencePipeline.forEach(Unknown Source)

at com.inductiveautomation.ignition.gateway.tags.config.BatchStructureChangeOperation.createTagStructureEvent(BatchStructureChangeOperation.java:64)

at com.inductiveautomation.ignition.gateway.tags.config.BatchStructureChangeOperation.execute(BatchStructureChangeOperation.java:85)

at com.inductiveautomation.ignition.gateway.tags.evaluation.BatchContextImpl$OpController.run(BatchContextImpl.java:240)

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)

```

---

<div class="post-metadata">

**Author:** ![ggross](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ggross/32/12668_2.png) [@ggross](https://forum.inductiveautomation.com/u/ggross)\
**Post date:** [November 17, 2022, 10:00pm UTC](https://forum.inductiveautomation.com/t/bug-6826-change-notification-error-flooding-the-log-after-updating-to-8-1-22/66541/12 "2022-11-17T22:00:22Z")

</div>

Awesome! Thanks for getting that for me!

---

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [November 17, 2022, 10:05pm UTC](https://forum.inductiveautomation.com/t/bug-6826-change-notification-error-flooding-the-log-after-updating-to-8-1-22/66541/13 "2022-11-17T22:05:08Z")

</div>

GW backup sent via PM

---

<div class="post-metadata">

**Author:** ![ggross](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ggross/32/12668_2.png) [@ggross](https://forum.inductiveautomation.com/u/ggross)\
**Post date:** [November 18, 2022, 12:09am UTC](https://forum.inductiveautomation.com/t/bug-6826-change-notification-error-flooding-the-log-after-updating-to-8-1-22/66541/14 "2022-11-18T00:09:29Z")

</div>

@nminchin, thank you for the stuff you provided. What is happening is, due to the history of this Gateway, there was a time when the Default tag provider had a `PROVIDERID` set to 0. Over time, this wasn't something that became expected, so when moving to 8.x the initial migration of Tag Providers didn't set the correct sequence in the `config.idb`, which causes any new providers added to get the same `PROVIDERID` as the `SYSTEM` internal provider.

Currently, your `System` and `default_fixed` provider have the same PROVIDERID and during startup, your tags in `default_fixed` are attempting to load into `System` which is a managed tag provider and it causing the errors you are seeing.

At this point it is best to work with support as there is some cleanup that would need to occur. We are looking into ways this can be fixed but the earliest it would be in a release would be 8.1.24. It is unclear why this now becoming an issue when it likely was not prior to this upgrade. It should have always been a problem, but we are currently trying to isolate what we changed to make the behavior change.

Thanks,  
Garth

---

<div class="post-metadata">

**Author:** ![justin.huggins](https://avatars.discourse-cdn.com/v4/letter/j/d07c76/32.png) [@justin.huggins](https://forum.inductiveautomation.com/u/justin.huggins)\
**Post date:** [November 21, 2022, 9:42pm UTC](https://forum.inductiveautomation.com/t/bug-6826-change-notification-error-flooding-the-log-after-updating-to-8-1-22/66541/15 "2022-11-21T21:42:30Z")

</div>

I am also getting much more data when adding that additional parameter to the conf file.

> java.lang.NullPointerException: null
> 
> at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.complex.UdtTypeDefinitionNode.getInvalidTypeBrowseValue(UdtTypeDefinitionNode.java:155)
> 
> at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.complex.AbstractComplexTagNode.getDisplayValue(AbstractComplexTagNode.java:143)
> 
> at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.BasicTagDefinition.getBrowseInfo(BasicTagDefinition.java:374)
> 
> at com.inductiveautomation.ignition.gateway.tags.config.BatchStructureChangeOperation.lambda$createTagStructureEvent$0(BatchStructureChangeOperation.java:64)
> 
> at java.base/java.util.stream.ReferencePipeline$3$1.accept(Unknown Source)
> 
> at java.base/java.util.LinkedList$LLSpliterator.forEachRemaining(Unknown Source)
> 
> at java.base/java.util.stream.AbstractPipeline.copyInto(Unknown Source)
> 
> at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(Unknown Source)
> 
> at java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(Unknown Source)
> 
> at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(Unknown Source)
> 
> at java.base/java.util.stream.AbstractPipeline.evaluate(Unknown Source)
> 
> at java.base/java.util.stream.ReferencePipeline.forEach(Unknown Source)
> 
> at com.inductiveautomation.ignition.gateway.tags.config.BatchStructureChangeOperation.createTagStructureEvent(BatchStructureChangeOperation.java:64)
> 
> at com.inductiveautomation.ignition.gateway.tags.config.BatchStructureChangeOperation.execute(BatchStructureChangeOperation.java:85)
> 
> at com.inductiveautomation.ignition.gateway.tags.evaluation.BatchContextImpl$OpController.run(BatchContextImpl.java:240)
> 
> 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)

---

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [November 21, 2022, 10:15pm UTC](https://forum.inductiveautomation.com/t/bug-6826-change-notification-error-flooding-the-log-after-updating-to-8-1-22/66541/16 "2022-11-21T22:15:30Z")

</div>

Are you seeing a `Gateway` folder in one of your own tag providers?

---

<div class="post-metadata">

**Author:** ![justin.huggins](https://avatars.discourse-cdn.com/v4/letter/j/d07c76/32.png) [@justin.huggins](https://forum.inductiveautomation.com/u/justin.huggins)\
**Post date:** [November 22, 2022, 8:27pm UTC](https://forum.inductiveautomation.com/t/bug-6826-change-notification-error-flooding-the-log-after-updating-to-8-1-22/66541/17 "2022-11-22T20:27:11Z")

</div>

does not seem to be one anywhere, not that I can find anyway.

---

<div class="post-metadata">

**Author:** ![Fabricio\_Colazo](https://avatars.discourse-cdn.com/v4/letter/f/a88e4f/32.png) [@Fabricio\_Colazo](https://forum.inductiveautomation.com/u/Fabricio_Colazo)\
**Post date:** [March 26, 2024, 5:52pm UTC](https://forum.inductiveautomation.com/t/bug-6826-change-notification-error-flooding-the-log-after-updating-to-8-1-22/66541/18 "2024-03-26T17:52:17Z")

</div>

Hello @ggross, I have the same issue. I migrated a project from vision 7.7.10 to perspective 8.1.32, could the problem be related to the import of the tags?

 ![Error](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/f/7fcd8cf4e6c61824d61d16e7fdceaab4b101c07a.jpeg)

---

<div class="post-metadata">

**Author:** ![ggross](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ggross/32/12668_2.png) [@ggross](https://forum.inductiveautomation.com/u/ggross)\
**Post date:** [March 26, 2024, 7:10pm UTC](https://forum.inductiveautomation.com/t/bug-6826-change-notification-error-flooding-the-log-after-updating-to-8-1-22/66541/19 "2024-03-26T19:10:39Z")

</div>

@Fabricio_Colazo I would recommend contacting support to investigate the problem. It looks probable that your Gateway is in a state that I noted above.

Garth