java.nio.BufferOverflowException

General Discussion
1

We have an Ignition (8.1.18) server where every two days a buffer overflow exception is happening. Once the buffer overflow occures, all execution of scripts are halted. Simply editing a script and saving it (or using EAM to push the tags/project), seems to temporarily resolve the problem. Has anyone a suggestion how to find the cause for this? Traceback (most recent call last):
File "<TimerScript:RSS_new/update_group_command_schedule @1,000ms >", line 2, in
File "module:group_command", line 495, in update_group_command_schedule
java.nio.BufferOverflowException
at java.base/java.nio.HeapByteBuffer.put(Unknown Source)
at org.python.core.io.BufferedWriter.write(BufferedWriter.java:41)
at org.python.core.io.BinaryIOWrapper.write(BinaryIOWrapper.java:118)
at org.python.core.io.TextIOWrapper.write(TextIOWrapper.java:260)
at org.python.core.PyFile.file_write(PyFile.java:456)
at org.python.core.PyFile.write(PyFile.java:460)
at org.python.core.StdoutWrapper.printToFile(StdoutWrapper.java:117)
at org.python.core.StdoutWrapper.print(StdoutWrapper.java:186)
at org.python.core.StdoutWrapper.println(StdoutWrapper.java:272)
at org.python.core.Py.println(Py.java:1905)
at org.python.pycode._pyx26915.update_group_command_schedule$8(module:group_command:497)
at org.python.pycode._pyx26915.call_function(module:group_command)
at org.python.core.PyTableCode.call(PyTableCode.java:173)
at org.python.core.PyBaseCode.call(PyBaseCode.java:119)
at org.python.core.PyFunction.call(PyFunction.java:406)
at org.python.pycode._pyx62.f$0(<TimerScript:RSS_new/update_group_command_schedule @1,000ms >:2)
at org.python.pycode._pyx62.call_function(<TimerScript:RSS_new/update_group_command_schedule @1,000ms >)
at org.python.core.PyTableCode.call(PyTableCode.java:173)
at org.python.core.PyCode.call(PyCode.java:18)
at org.python.core.Py.runCode(Py.java:1687)
at com.inductiveautomation.ignition.common.script.ScriptManager.runCode(ScriptManager.java:796)
at com.inductiveautomation.ignition.gateway.project.ProjectScriptLifecycle$TrackingProjectScriptManager.runCode(ProjectScriptLifecycle.java:819)
at com.inductiveautomation.ignition.common.script.ScriptManager.runCode(ScriptManager.java:748)
at com.inductiveautomation.ignition.gateway.project.ProjectScriptLifecycle$TrackingProjectScriptManager.runCode(ProjectScriptLifecycle.java:800)
at com.inductiveautomation.ignition.common.script.TimerScriptTask.run(TimerScriptTask.java:90)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.runAndReset(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)
at java.base/java.lang.Thread.run(Unknown Source)
java.nio.BufferOverflowException: java.nio.BufferOverflowException

8.1.18 (b2022061518)
Azul Systems, Inc. 11.0.15

image
image1255×698 59.2 KB

image
image1073×1016 65.4 KB

image
image1035×617 40.9 KB

image
image1131×926 28.5 KB

image
image988×630 46.1 KB

2

Show your code for this event. (Remember to use the "preformatted text" in the forum's comment editor. Please also edit your OP and fix the pasted backtrace likewise.)

3

Root cause is probably massive flooding of print statements in that timer. Maybe inside a loop inadvertently.

4

Yes, it is also my assumption. It was very likely caused by timer started script having print statements for debugging, so I've removed al print statements from the said scripts. We will see if it stabilises