Node restarts caused by Out Of Memory condition requesting variables from out of the box "Raise Issue" record producer - Known Error

Node restarts caused by Out Of Memory condition requesting variables from out of the box "Raise Issue" record producer Description The "Raise Issue" [sc_cat_item_e85a62ab93e4121055431cbf6489183b] catalog item includes two "Lookup Select Box" variables, "Urgency" and "Preferred methods of contact," which are not well defined. Both are set up on the "Incident"/"Task" tables without a reference qualifier. As these tables grow, retrieving values for these select boxes becomes more time-consuming and uses more memory, which can eventually lead to OutOfMemory errors and cause nodes to restart.

Steps to Reproduce

Steps to Reproduce:

1) Login to an instance as an admin user 2) Activate the "Asset Mangement Common" [sn_itam_common] plugin. 3) Create a lot of incidents. 4) Navigate to the System Diagnostics > Session Debug > Debug SQL (Detailed) module. Click on the "Confirm" button. 5) Navigate to the REST API Explorer (/$restapi.do) 6) Select the "sn_sc" Namespace 7) Select the "Service Catalog API" REST API. 8) Click on the "Variables of an item (GET)" function. 9) Enter the following variables:

sys_id: e85a62ab93e4121055431cbf6489183b

10) Click on the "Send" button.

Expected Results: We should get the response very quickly as there are only a few choices for the urgency and contact_type fields.

Actual Results: It takes a long time and we can even run out of memory if the incident table has a lot of rows.

Workaround You can follow any of the below options to resolve the issue: Option 1) The catalog item in question - "Raise Issue", is part of the "Asset Mangement Common" [sn_itam_common] plugin. From the version 12.1.0 of this plugin, the two variables that are causing the problem are now defined correctly as choice fields. The solution to this problem is to upgrade the "Asset Mangement Common" [sn_itam_common] plugin to version 12.1.0 or higher.

Option 2) Alternatively, you can resolve the issue by importing the two attached files from PRB1955735: item_option_new_1695fe679328121055431cbf648918a3.xml item_option_new_87d2f2e39328121055431cbf64891875.xml