# High CPU Usage after Error in logs

**URL:** <https://forum.inductiveautomation.com/t/high-cpu-usage-after-error-in-logs/37200>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [July 29, 2020, 6:07pm UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-after-error-in-logs/37200 "2020-07-29T18:07:51Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![zacht](https://avatars.discourse-cdn.com/v4/letter/z/ea5d25/32.png) [@zacht](https://forum.inductiveautomation.com/u/zacht)\
**Post date:** [July 29, 2020, 6:07pm UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-after-error-in-logs/37200/1 "2020-07-29T18:07:51Z")

</div>

We had an issue where gateway CPU usage rose dramatically as pictured. This rise corresponds with this error in the gateway wrapper log:

```auto
INFO | jvm 1 | 2020/07/16 21:24:21 | W [c.i.x.d.a.ScheduledRequest] [04:24:21]: Uncaught Throwable invoking class com.inductiveautomation.xopc.drivers.allenbradley.requests.ABControlLogixReadRequest#receiveMessage: java.lang.NullPointerException 

```

It was obviously awhile before we noticed. When we did, looking at the threads we were able to determine one device connection was consuming 40-60% CPU. It is a CompactLogix PLC using the AB Legacy driver. Disabling and enabling this connection caused the CPU usage to drop back to normal levels. We didn’t take any thread dumps, but if we see this issue again we will.

Can anyone shed some light on the error we found in the logs or offer other ideas as to what caused this?

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/4/0443960fb190d2c2864a11625f5c542ca368ec39.png)  
Ignition Version 8.0.10

---

<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:** [July 29, 2020, 6:15pm UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-after-error-in-logs/37200/2 "2020-07-29T18:15:42Z")

</div>

Whatever happened is likely a bug in the legacy driver.

If you can get a thread dump and logs if/when it happens again that may help track down what’s going on.

---

<div class="post-metadata">

**Author:** ![zacht](https://avatars.discourse-cdn.com/v4/letter/z/ea5d25/32.png) [@zacht](https://forum.inductiveautomation.com/u/zacht)\
**Post date:** [July 29, 2020, 6:27pm UTC](https://forum.inductiveautomation.com/t/high-cpu-usage-after-error-in-logs/37200/3 "2020-07-29T18:27:56Z")

</div>

We’ll definitely do that. Thanks for the input.