Basic Request Cycle

[kaushik.shah]

Hello There,

I have a gateway log filled with this :

Its an Siemens 1500 CPU.
Does anyone have familiarity with something similar?

Thanks so much in advance

[Kevin.Herron]

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.

[kaushik.shah]

It's just a null pointer exception.

Sure

[PGriffith]

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

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.

[kaushik.shah]

@PGriffith

useful

I see, I'll set this up in weekend and will watch next week for the details.
Thank you @PGriffith , @Kevin.Herron

[kaushik.shah]

Hello @PGriffith ,
I did updated ignition conf file and restarted the server. I still do get this errors without much of a stack.

[pturmel]

That's a much more helpful stack trace. I expect @Kevin.Herron to pop in any moment with new bug number assigned. (:

[Kevin.Herron]

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.

[kaushik.shah]

@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