# Basic Request Cycle **URL:** \ **Category:** Ignition\ **Tags:** ignition80\ **Created:** [December 6, 2022, 4:51pm UTC](https://forum.inductiveautomation.com/t/basic-request-cycle/67300 "2022-12-06T16:51:55Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![kaushik.shah](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@kaushik.shah](https://forum.inductiveautomation.com/u/kaushik.shah)\ **Post date:** [December 6, 2022, 4:51pm UTC](https://forum.inductiveautomation.com/t/basic-request-cycle/67300/1 "2022-12-06T16:51:55Z")
Hello There, I have a gateway log filled with this : ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/b/0bfa43dee447e5cf42c364ab2142ceb7b9c5e7aa.png) Its an Siemens 1500 CPU. Does anyone have familiarity with something similar? Thanks so much in advance ---
**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:** [December 6, 2022, 5:03pm UTC](https://forum.inductiveautomation.com/t/basic-request-cycle/67300/2 "2022-12-06T17:03:04Z")
If you click the "+" to expand the message what does it say under there? I think I may have seen a bug like this in the past when invalid/unparseable addresses made their way to the driver, but I'm not sure. You may have to work with support to get your logs and check addresses. ---
**Author:** ![kaushik.shah](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@kaushik.shah](https://forum.inductiveautomation.com/u/kaushik.shah)\ **Post date:** [December 6, 2022, 5:04pm UTC](https://forum.inductiveautomation.com/t/basic-request-cycle/67300/3 "2022-12-06T17:04:25Z")
It's just a null pointer exception. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/6/56a9dc10a8141929588d90177cb74e0adcf6334a.png) Sure ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [December 6, 2022, 5:12pm UTC](https://forum.inductiveautomation.com/t/basic-request-cycle/67300/4 "2022-12-06T17:12:30Z")
You'll need to update the ignition.conf file to capture a useful stack trace from the repeated exception: > [@\[BUG-6826\]: Change notification error flooding the log after updating to 8.1.22](https://forum.inductiveautomation.com/t/bug-6826-change-notification-error-flooding-the-log-after-updating-to-8-1-22/66541/7): > > 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)? wrapper.java.additional.6=-XX:-OmitStackTraceInFastThrow On restart, in theory, it should start providing a stack trace. Thanks, Garth Support can help you with that process, as well. ---
**Author:** ![kaushik.shah](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@kaushik.shah](https://forum.inductiveautomation.com/u/kaushik.shah)\ **Post date:** [December 6, 2022, 5:24pm UTC](https://forum.inductiveautomation.com/t/basic-request-cycle/67300/5 "2022-12-06T17:24:02Z")
> [@paul-griffith](#): > > useful I see, I'll set this up in weekend and will watch next week for the details. Thank you @paul-griffith , @Kevin.Herron ---
**Author:** ![kaushik.shah](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@kaushik.shah](https://forum.inductiveautomation.com/u/kaushik.shah)\ **Post date:** [December 14, 2022, 12:21pm UTC](https://forum.inductiveautomation.com/t/basic-request-cycle/67300/6 "2022-12-14T12:21:31Z")
Hello @paul-griffith , I did updated ignition conf file and restarted the server. I still do get this errors without much of a stack. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/a/aa90aeb466ee3c2cb2fd2109ab032fc33fb489d6.png) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/0/f0562c9b609a0ad2fb806f2f7e7e46f74c224f96.png) ---
**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:** [December 14, 2022, 2:35pm UTC](https://forum.inductiveautomation.com/t/basic-request-cycle/67300/7 "2022-12-14T14:35:51Z")
That's a much more helpful stack trace. I expect @Kevin.Herron to pop in any moment with new bug number assigned. (: ---
**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:** [December 14, 2022, 2:49pm UTC](https://forum.inductiveautomation.com/t/basic-request-cycle/67300/8 "2022-12-14T14:49:31Z")
Yes, looks like a bug I can make a ticket for. You've probably got a script somewhere that is trying to write a null value. You'll have to figure out where that is and fix it for now. ---
**Author:** ![kaushik.shah](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@kaushik.shah](https://forum.inductiveautomation.com/u/kaushik.shah)\ **Post date:** [December 14, 2022, 2:53pm UTC](https://forum.inductiveautomation.com/t/basic-request-cycle/67300/9 "2022-12-14T14:53:20Z")
> [@Kevin.Herron](#): > > ou've probably got a script somewhere that is trying to write a null value. You'll have to figure out where that is and fix it for now. hmm, makes sense. Thanks Kevin