# Wrapper Log Filling with Exception in thread

**URL:** <https://forum.inductiveautomation.com/t/wrapper-log-filling-with-exception-in-thread/34084>\
**Category:** Ignition\
**Created:** [April 21, 2020, 4:56pm UTC](https://forum.inductiveautomation.com/t/wrapper-log-filling-with-exception-in-thread/34084 "2020-04-21T16:56:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mstone](https://avatars.discourse-cdn.com/v4/letter/m/ec9cab/32.png) [@mstone](https://forum.inductiveautomation.com/u/mstone)\
**Post date:** [April 21, 2020, 4:56pm UTC](https://forum.inductiveautomation.com/t/wrapper-log-filling-with-exception-in-thread/34084/1 "2020-04-21T16:56:08Z")

</div>

It appears to reference a thread that isn’t listed on the gateway Threads page. How do I get more info on this to find the problem? Here is a paste:  
Exception in thread Thread-1697138:Traceback (most recent call last):  
INFO | jvm 1 | 2020/04/21 16:29:50 | File “/var/lib/ignition/user-lib/pylib/threading.py”, line 222, in \_Thread\_\_bootstrap  
INFO | jvm 1 | 2020/04/21 16:29:50 | self.run()  
INFO | jvm 1 | 2020/04/21 16:29:50 | File “/var/lib/ignition/user-lib/pylib/threading.py”, line 360, in run  
INFO | jvm 1 | 2020/04/21 16:29:50 | self.function(\*self.args, \*\*self.kwargs)

If I look, there is no thread “Thread-1697138” that I can find. About 90 of these are hitting the wrapper log every 6 seconds or so.  
Ignition 8.0.10(b2020031912) Linux, java version 11.0.6+10LTS

Thanks

---

<div class="post-metadata">

**Author:** ![mstone](https://avatars.discourse-cdn.com/v4/letter/m/ec9cab/32.png) [@mstone](https://forum.inductiveautomation.com/u/mstone)\
**Post date:** [June 4, 2020, 12:28pm UTC](https://forum.inductiveautomation.com/t/wrapper-log-filling-with-exception-in-thread/34084/2 "2020-06-04T12:28:24Z")

</div>

This was resolved by Support. Root cause was a gateway timer script that used threading. Support advised I should use time.sleep instead of threading. This worked.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [June 4, 2020, 1:41pm UTC](https://forum.inductiveautomation.com/t/wrapper-log-filling-with-exception-in-thread/34084/3 "2020-06-04T13:41:10Z")

</div>

> [@mstone](#):
>
> Support advised I should use time.sleep instead of threading.

_ **Support recommended this?** _ Somebody needs to be retrained. Expect those sleep calls to eventually cause strange performance side effects in other parts of Ignition.

Seriously, no form of sleep should be used outside of a thread started by system.util.invokeAsynchronous.

You weren't finding those threads because that error is fatal. The thread wouldn't exist after the error was logged.