Issue Summary

Assets object view generates huge heap consumption when there are many connected tickets to the object

This is reproducible on Data Center: yes

Steps to Reproduce

1. Create an object in an object type and connect it to many Jira issues (ex. > 100 Jira issues).
2. Make sure that the object type also has outbound references and link some references to the same object.
3. Browse the object view for this object and also the connected tickets tab. The following 2 endpoint are called:

/rest/insight-am/1/assets/KEY/outboundreferences
/rest/insight-am/1/assets/KEY/connectedtickets

What happen is that while the object view has pagination at the moment the code has no limit and 2 behaviours can be observed:

• a query is executed across all the Jira connected tickets (disregarding the pagination) resulting in huge memory consumption.
• for the outbound references a query is executed for each references also calling the connected tickets of the referenced objects.

Both the above behaviour results in huge memory consumption and can lead the instance/node to crash if the object has a huge number of connected tickets and/or outbound references having a lot connected tickets.

Expected Results

Query should run on connected objects respecting the 15 results default limit pagination and query for referenced objects should not iterate across the connected tickets of references.

Actual Results

A query is executed across all the Jira connected tickets (disregarding the pagination) resulting in huge memory consumption and for the outbound references a query is executed for each references also calling the connected tickets of the referenced objects.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available