CF-3607057

Title

Prevent dumping an ORM object with lots of relations from causing OoM errors.

Description

Dumping variables from a complex ORM application runs the risk of causing a java.lang.OutOfMemoryError caused by too many levels of ORM relationships attempting to be dumping.

This can be partially mitigated with the top attribute of cfdump/writedump, but these do not solve the problem entirely (and get in the way of dumping nested structures).

There should be an admin setting to configure how deep into an ORM object that dumping should go - effectively the same behaviour as top, applied globally but only for ORM objects.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3607057

External Customer Info:
External Company:  
External Customer Name: boughtonp
External Customer Email:

Comments

The top attribute has been added for this purpose only. The application should take care of using top. Moreover dump is only for debugging and not for production.

Comment by Rupesh K.

09/06/2013 06:36:45 GMT

The status of this issue is NOT withdrawn! > The top attribute has been added for this purpose only. No, the top attribute was added in MX7, before CF had ORM. It does NOT solve this problem and prevents arrays and structs from being dumped correctly. > Moreover dump is only for debugging and not for production. Seriously? That does NOT make this not an issue.

Comment by External U.

10/17/2014 05:26:36 GMT

Status:

Closed

Details

Date Created:

08/05/2013

Component:

ORM Support

Version:

10.0

Failure Type

Enhancement Request

Found In Build:

Final

Fixed In Build:

Priority:

Trivial

Frequency:

Unknown

System:

Platforms All

Browser:

Resolution

Withdrawn

Reason Code:

NotABug

Votes: