Multiple Node Restarts due to Out-Of-Memory (OOM) – Anyone else experiencing this recently?

[Pawel Barcik]

Hello Community,

We have recently started encountering a critical issue on our Production instance where multiple application nodes are unexpectedly restarting due to Out-Of-Memory (OOM) errors.

According to Now Support (HI Case analysis), the heap dump points to a specific long-running Scheduled Job / Script Include responsible for data integration Support's immediate advice was to optimize our script, reduce the data set, or implement batching/pagination.

However, here is the catch: this integration script and the data volume have been running exactly the same way for several years without a single issue. Absolutely no changes or code modifications were introduced on our side prior to these OOM crashes.

This makes us suspect that there might have been a recent underlying platform change, infrastructure update, or altered JVM memory allocation limits on the ServiceNow side that is causing the platform to fail under standard, long-term operational workloads.

Has anyone else experienced a sudden spike in Out-Of-Memory errors or unexpected node restarts during large data imports or scheduled jobs recently? If you faced a similar situation, how did you challenge support, or what was the actual root cause?

Any insights or shared experiences would be highly appreciated!