What causes "domsrvr 5440 FATAL init.c 363 Operator :: new cannot allocate XXXX bytes." in the stdlog?
search cancel

What causes "domsrvr 5440 FATAL init.c 363 Operator :: new cannot allocate XXXX bytes." in the stdlog?

book

Article ID: 11283

calendar_today

Updated On:

Products

CA Service Desk Manager CA Service Management - Service Desk Manager

Issue/Introduction

In Service Desk, sometimes the stdlogs are filled with the error message "domsrvr 5440 FATAL init.c 363 Operator :: new cannot allocate XXXX bytes.". This document explains the reason and the steps to resolve this error.

What is the reason behind the "Operator :: new cannot allocate XXXX bytes?

Environment

Release: SDMU0M99000-14.1-Service Desk Manager-Full License
Component:

Resolution

This message indicates that the process attempted to allocate memory from the Operating System, however there was no memory available.

One thing to keep in mind is that processes in Windows have a maximum memory allocation of 2 GB permitted.  Any higher and an attempt to allocate further memory will result in the given message in the SDM stdlogs.

To resolve these issues, the best thing to do is track Memory Utilization per process ('pslist' (downloadable from Microsoft), Task Manager on Windows, 'top' on Unix.  One may also consider running the interval logging on the SDM Server to monitor process progression.

Several causes may result in the given message and will require monitoring of the install to determine the cause. 

One possible cause of this can be "preload" files under NX_ROOT/site/mods/majic.  These will tell the domsrvr to cache an entire table on startup which may not be appropriate, given the size of some Service Desk tables.