What is a 'mmap failed for CEN and END part of zip file' message and why are these impactfulSummaryThis article is intended to provide further detail around a new ServiceNow Alert Type (ServiceNow Monitoring). In most cases relief has been achieved before the case was opened and reason for the case is notify the customer that an event occurred and for ServiceNow to work on the most likely cause analysis. These messages are an indication of a memory issue impacting one node related to Native Memory or Virtual Memory. ServiceNow uses a 32-BIT JVM (node) which has a hard limit at the OS layer of up to about 4 GB. When the JVM's (node's) PID hits this hard limit the OS cannot allocate more memory resulting in a failure (most common customer facing issue is a blank screen), at which point the node in a broken state and requires a restart to recover. Note: These messages will only be present in the wrapper logs or as a ZipException in the localhost logs (Log Utilities). It is not expected that customer would catch or be able to troubleshoot this issue. Wrapper Log: INFO | jvm 4 | 2021/02/07 11:35:09.638 | mmap failed for CEN and END part of zip fileLocalhost Log: 2021-02-07 04:00:05 (369) worker.4 worker.4 txid=615fddfb1b8a SEVERE *** ERROR *** java.util.zip.ZipException: error in opening zip filejava.lang.IllegalStateException: java.util.zip.ZipException: error in opening zip file The common outcome for this issue is a user reporting a blank screen when attempting to access a node that is impacted. This is a symptom of the issue versus the cause. The same is true for the related messages in the logs. Like a JVM heap space Out of memory error, the causes are endless and cannot be fully resolved until the underlining related code that triggered the issue is changed/fixed. In most cases of the 'mmap failed for CEN and END part of zip file' issue, the process/transaction/job that caused the issue occurred days or hours before the JVM (node) entered into a broken state. ServiceNow has identified multiple problems that can lead to this issue but in some cases no causes could be identified. Common Issue: Customers reporting users on one node are receiving blank screens and clearing the browser cache appears to fix the issue as the user moves to a different node in the instance cluster. Related Case Types: 1. (Priority 4) Subject: Node INSTANCENODE#### was impacted (no impact currently) by the 'mmap failed for CEN and END part of zip file' issue Summary: ServiceNow automatically detected and provided relief (node restart). A ServiceNow engineers will need to review to determine cause. Please allow up to a week for this to be completed. In some cases ServiceNow will be unable to provide a cause and we apologize. We are aware that that this ideally and have multiple teams engaged in a larger project to fix this issue. 2. (Priority 2) Subject: Node INSTANCENODE#### is impacted by the 'mmap failed for CEN and END part of zip file' issue Summary: ServiceNow detected the issue but could not automatically provide relief and the case as been route to an ServiceNow engineers to provide relief (node restart) and then review to determine cause.