# Major latency (but fix after reboot) **URL:** \ **Category:** General Discussion\ **Tags:** ignition79\ **Created:** [February 16, 2022, 7:36am UTC](https://forum.inductiveautomation.com/t/major-latency-but-fix-after-reboot/56195 "2022-02-16T07:36:39Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![steven.oosterbosch](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@steven.oosterbosch](https://forum.inductiveautomation.com/u/steven.oosterbosch)\ **Post date:** [February 16, 2022, 7:36am UTC](https://forum.inductiveautomation.com/t/major-latency-but-fix-after-reboot/56195/1 "2022-02-16T07:36:39Z")
Hi, Today, well tonight actually, we had a major incident that reduced the connectivity from gateway to PLC’s. Unfortunatly it filled the entire logg, so I can not go to the root cause. I think. But I did found this; No optimized AddressBlock list found for items: [com.inductiveautomation.xopc.server.addressspace.contexts.WriteContext$PendingDriverWrite@5d2b7cf, com.inductiveautomation.xopc.server.addressspace.contexts.WriteContext$PendingDriverWrite@54d38421, com.inductiveautomation.xopc.server.addressspace.contexts.WriteContext$PendingDriverWrite@133810ef, com.inductiveautomation.xopc.server.addressspace.contexts.WriteContext$PendingDriverWrite@1dd6b9a3, com.inductiveautomation.xopc.server.addressspace.contexts.WriteContext$PendingDriverWrite@daa1919, com.inductiveautomation.xopc.server.addressspace.contexts.WriteContext$PendingDriverWrite@45906601, com.inductiveautomation.xopc.server.addressspace.contexts.WriteContext$PendingDriverWrite@167ca934, com.inductiveautomation.xopc.server.addressspace.contexts.WriteContext$PendingDriverWrite@3ecf01f9, com.inductiveautomation.xopc.server.addressspace.contexts.WriteContext$PendingDriverWrite@63f0b5e8, com.inductiveautomation.xopc.server.addressspace.contexts.WriteContext$PendingDriverWrite@251677f9, com.inductiveautomation.xopc.server.addressspace.contexts.WriteContext$PendingDriverWrite@56504f66, com.inductiveautomation.xopc.server.addressspace.contexts.WriteContext$PendingDriverWrite@10d64c9c] Can somebody give me an explanation what this is about? KR, Steven O ---
**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\ **Post date:** [February 17, 2022, 2:58pm UTC](https://forum.inductiveautomation.com/t/major-latency-but-fix-after-reboot/56195/2 "2022-02-17T14:58:23Z")
> [@S7400 driver Error caused by Gateway Tag Change Script](https://forum.inductiveautomation.com/t/s7400-driver-error-caused-by-gateway-tag-change-script/40762/2): > > What version of Ignition are you using? This looks like it could be the result of a bug that was fixed in 7.9.16. ---
**Author:** ![steven.oosterbosch](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@steven.oosterbosch](https://forum.inductiveautomation.com/u/steven.oosterbosch)\ **Post date:** [February 17, 2022, 3:04pm UTC](https://forum.inductiveautomation.com/t/major-latency-but-fix-after-reboot/56195/3 "2022-02-17T15:04:07Z")
We are indeed using 7.9. But I don’t know if we are using .16. Where can I find this information? And, it has been running smoothly for at least 9 months. What could have triggered this? ---
**Author:** ![steven.oosterbosch](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@steven.oosterbosch](https://forum.inductiveautomation.com/u/steven.oosterbosch)\ **Post date:** [February 17, 2022, 3:09pm UTC](https://forum.inductiveautomation.com/t/major-latency-but-fix-after-reboot/56195/4 "2022-02-17T15:09:42Z")
We are using 7.9.13 (64-bit). ---
**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\ **Post date:** [February 17, 2022, 3:43pm UTC](https://forum.inductiveautomation.com/t/major-latency-but-fix-after-reboot/56195/5 "2022-02-17T15:43:34Z")
From other similar threads it seems to be tied to the Siemens driver. Either way, it's probably a good idea to upgrade to the latest 7.9 version. > [@Weekly 7.9 Changelogs - 2020](https://forum.inductiveautomation.com/t/weekly-7-9-changelogs-2020/35731/9): > > Nightly Changelog: 7.9.15-b20200811 Alarm Notification 16841: Alarm Pipeline Block UI takes long to connect pipeline block lines Improved performance of Alarm Pipeline Block UI. Ignition Platform 16926:IllegalStateException from S+F cache updater task Prevent IllegalStateException from S+F cleanup thread. 16070: Alarm Event Missing Information After Alarm Enabled Property Toggled Fixed an issue where alarm event information was lost if the event was cleared while the alarm configuration wa… ---
**Author:** ![steven.oosterbosch](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@steven.oosterbosch](https://forum.inductiveautomation.com/u/steven.oosterbosch)\ **Post date:** [February 18, 2022, 7:55am UTC](https://forum.inductiveautomation.com/t/major-latency-but-fix-after-reboot/56195/6 "2022-02-18T07:55:13Z")
Hi Jordan, You are correct, we also suspect it to be connected to the Siemens driver. I am planning to update tomorrow afternone when the plan is not operational. Any idea what could have triggered this? KR Steven ---
**Author:** ![steven.oosterbosch](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@steven.oosterbosch](https://forum.inductiveautomation.com/u/steven.oosterbosch)\ **Post date:** [February 18, 2022, 8:32am UTC](https://forum.inductiveautomation.com/t/major-latency-but-fix-after-reboot/56195/7 "2022-02-18T08:32:10Z")
I also notice an enormous amount of CPU usage due to Iginition. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/6/f6fbcf442d2a464af3fbad272e9f36b1e505d65f.png) Maybe it is time for me to contact support… ---
**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\ **Post date:** [February 18, 2022, 9:51am UTC](https://forum.inductiveautomation.com/t/major-latency-but-fix-after-reboot/56195/8 "2022-02-18T09:51:43Z")
The changelog specifies multiple writes to the same address. So it could be from anything writing to the PLC. Any new or changed scripts? I’d contact support after upgrading, because that will be one of the first things they will tell you to try. 😉 ---
**Author:** ![steven.oosterbosch](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@steven.oosterbosch](https://forum.inductiveautomation.com/u/steven.oosterbosch)\ **Post date:** [February 18, 2022, 9:59am UTC](https://forum.inductiveautomation.com/t/major-latency-but-fix-after-reboot/56195/9 "2022-02-18T09:59:47Z")
The problem is that our gateway serves multiple plants across Europe. When I asked other plants they all respond that nothing has been changed… 🙃 I am going to update the version tomorrow, and if this does not help I’ll revert back to Friday last week. ---
**Author:** ![steven.oosterbosch](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@steven.oosterbosch](https://forum.inductiveautomation.com/u/steven.oosterbosch)\ **Post date:** [February 18, 2022, 11:09am UTC](https://forum.inductiveautomation.com/t/major-latency-but-fix-after-reboot/56195/10 "2022-02-18T11:09:09Z")
I was able to find the problem. When I make a report, some threads skyrocket. Threaddump below. [Ignition-HCR-SCADA\_thread\_dump20220218-113436.txt](https://forum.inductiveautomation.com/uploads/short-url/yRgn3eGCNGWuVmAyI9bBs6XqsVP.txt) (166.8 KB) [Ignition-HCR-SCADA\_thread\_dump20220218-120734.txt](https://forum.inductiveautomation.com/uploads/short-url/3PQtvHxTy4DRDh40iRyN0iApunl.txt) (336.6 KB) ---
**Author:** ![steven.oosterbosch](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@steven.oosterbosch](https://forum.inductiveautomation.com/u/steven.oosterbosch)\ **Post date:** [February 18, 2022, 2:27pm UTC](https://forum.inductiveautomation.com/t/major-latency-but-fix-after-reboot/56195/11 "2022-02-18T14:27:20Z")
This is the thread detail regarding the problem; Thread [webserver-351] id=351, (RUNNABLE) org.python.core.PyInteger.asPyInteger(PyInteger.java:99) org.python.core.PyInteger.int\_new(PyInteger.java:61) org.python.core.PyInteger$exposed\_\_\_new\_\_.new\_impl(Unknown Source) org.python.core.PyType.invokeNew(PyType.java:466) org.python.core.PyType.type\_\_\_call\_\_(PyType.java:1558) org.python.core.PyType. **call** (PyType.java:1548) org.python.core.PyObject. **call** (PyObject.java:387) org.python.core.PyObject. **call** (PyObject.java:391) org.python.pycode.\_pyx28.PersTabelMeldingen$2(:154) org.python.pycode.\_pyx28.call\_function() org.python.core.PyTableCode.call(PyTableCode.java:165) org.python.core.PyBaseCode.call(PyBaseCode.java:120) org.python.core.PyFunction. **call** (PyFunction.java:307) org.python.pycode._pyx40.updateData$1(:155) org.python.pycode.pyx40.call\_function() org.python.core.PyTableCode.call(PyTableCode.java:165) org.python.core.PyBaseCode.call(PyBaseCode.java:301) org.python.core.PyFunction.function\_\_\_call_(PyFunction.java:376) org.python.core.PyFunction. **call** (PyFunction.java:371) org.python.core.PyFunction. **call** (PyFunction.java:361) org.python.core.PyFunction. **call** (PyFunction.java:356) com.inductiveautomation.ignition.common.script.ScriptManager.runFunction(ScriptManager.java:649) com.inductiveautomation.ignition.common.script.ScriptManager$ScriptFunctionImpl.invoke(ScriptManager.java:759) com.inductiveautomation.reporting.gateway.data.ScriptReportDataSource.gatherData(ScriptReportDataSource.java:57) com.inductiveautomation.reporting.gateway.ReportingGatewayHook.getReportData(ReportingGatewayHook.java:338) com.inductiveautomation.reporting.gateway.ReportingGatewayHook$RPC.getReportData(ReportingGatewayHook.java:529) sun.reflect.GeneratedMethodAccessor161.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) java.lang.reflect.Method.invoke(Unknown Source) com.inductiveautomation.ignition.gateway.servlets.gateway.functions.ModuleInvoke.invoke(ModuleInvoke.java:172) com.inductiveautomation.ignition.gateway.servlets.Gateway.doPost(Gateway.java:405) javax.servlet.http.HttpServlet.service(HttpServlet.java:707) javax.servlet.http.HttpServlet.service(HttpServlet.java:790) com.inductiveautomation.ignition.gateway.bootstrap.MapServlet.service(MapServlet.java:85) org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:837) org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583) org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1160) org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511) org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1092) org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:52) org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) org.eclipse.jetty.server.Server.handle(Server.java:518) org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:308) org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:244) org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273) org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:246) org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:156) org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654) org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572) java.lang.Thread.run(Unknown Source) ---
**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:** [February 18, 2022, 3:20pm UTC](https://forum.inductiveautomation.com/t/major-latency-but-fix-after-reboot/56195/12 "2022-02-18T15:20:43Z")
It seems you have a report with a script data source that is burning a lot of CPU while running. This script would be something you or someone else on your project wrote, so maybe take a closer look at those. ---
**Author:** ![steven.oosterbosch](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@steven.oosterbosch](https://forum.inductiveautomation.com/u/steven.oosterbosch)\ **Post date:** [February 18, 2022, 3:24pm UTC](https://forum.inductiveautomation.com/t/major-latency-but-fix-after-reboot/56195/13 "2022-02-18T15:24:55Z")
Hi kevin, Thank you for the response. I am thinking the same thing. But I do not recall working on any script. Neither does my colleague. Are the scripts “numbered” by any way in Ignition so I can start looking for anything specific? Letts just say there are a lot of scripts running… KR, Steven ---
**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:** [February 18, 2022, 3:31pm UTC](https://forum.inductiveautomation.com/t/major-latency-but-fix-after-reboot/56195/14 "2022-02-18T15:31:36Z")
It’s not just any script, it’s one that is part of a report: [Scripting Data Source - Ignition User Manual 8.1 - Ignition Documentation](https://docs.inductiveautomation.com/display/DOC81/Scripting+Data+Source) Not sure there’s any more detail that can be extracted from your thread dump. ---
**Author:** ![steven.oosterbosch](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@steven.oosterbosch](https://forum.inductiveautomation.com/u/steven.oosterbosch)\ **Post date:** [February 18, 2022, 3:34pm UTC](https://forum.inductiveautomation.com/t/major-latency-but-fix-after-reboot/56195/15 "2022-02-18T15:34:22Z")
Hi Kevin, I found the issue, the tag connection to an transaction group was wrong. Actually it was double to the same tagg. None the less I am updating to Ignition 7.9.16 tomorrow. I have noticed small buggs like not being able to cancell a report while it is running and so on. Maybe these smaller issues in the gateway are resolved. Thanks everybody for the support!