The events processor runs the node out of memory when processing email notifications for records which contain un-closed "<" tags.

Steps to Reproduce

Steps to replicate the bad worknote causing a stuck event issue. 
From any open INT:
  1. Add the text in the attachment (worknote_Comments.txt.zip) as a worknote comment
  2. In the Event logs for events under queued state you will see a corresponding incident.commented event which remains in queued state and not get processed (remains in queued state). 
  3. This also results in OOM [and automatic restart of node that picked up the event to process].


Since the event is not processed, this process repeats until the event is moved to an error state.

Move the event to error state.

Related Problem: PRB1158590

Seen In

Berlin Patch 1
Berlin Patch 4
Calgary Patch 2 Hot Fix 5
Eureka Patch 7
Fuji Patch 10

Intended Fix Version

Jakarta Patch 11
Kingston Patch 10

Fixed In


Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-08-13 10:23:52