NullPointerException- Spike Arrest Policy

[ankitkrsingha]

Hi Guys,

Getting 500 Internal Server Error,

{ "fault": { "faultstring": "NullPointerException", "detail": { "errorcode": "Internal Server Error" } } }

Though the Spike Arrest set is a default configuration:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<SpikeArrest async="false" continueOnError="false" enabled="false" name="spike-arrest"> <DisplayName>spike arrest</DisplayName>

<Rate>30ps</Rate> </SpikeArrest>

Though the Spike Arrest policy is having default configuration:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <SpikeArrest async="false" continueOnError="false" enabled="false" name="spike-arrest"> <DisplayName>spike arrest</DisplayName> <Rate>30ps</Rate> </SpikeArrest>

[dchiesa1]

Always? Only sporadically? Under which specific circumstances do you see this behavior?

Can you reliably reproduce it?

Describe the Edge configuration - public cloud? OPDK? If so, which version?

[ankitkrsingha]

It started occurring since last 2 days, though I receive a proper violation message("SpikeArrestViolation"), but that's very less.

for e.g in a trace session out of 20 calls, I recieve 2-3 "SpikeArrestViolation" response.

Edge configuration: On-Premise

Version 4.18.05.00

[dchiesa1]

You can get more details by looking in the system.log for the MPs.

Scan for NullPointerException.

if you can show us the log messages surrounding that - immediately before and after - then it will help us in diagnosing the problem.

[santoshghalsasi]

Hi Ankit, Dino,

What was the resolution on this error? We are also getting similar error on on-prem instance 4.10.05.

Thanks,

Santosh

[#6]

@Santosh you can check if you have any reference variable in the policy. If yes then check that variable is available in the flow and is not null.