502 Bad Gateway nginx/1.10.0 (Ubuntu

Hi devs, we’re having som problems woth a 2.24 instance that crashes. This is what we find in the logs (below) - the warning repeats itself until tomcat crashes. Any advice?

Regards

Olav

···
  • INFO 2016-12-05 13:08:02,235 ‘lamin’ update org.hisp.dhis.program.ProgramInstance, uid: vACQtdeeQ11 (AuditLogUtil.java [tomcat-http-10])
  • WARN 2016-12-05 13:08:31,680 The configured limit of 1,000 object references was reached while attempting to calculate the size of the object graph. Severe performance degradation could occur if the sizing operation continues. This can be avoided by setting the CacheManger or Cache elements maxDepthExceededBehavior to “abort” or adding stop points with @IgnoreSizeOf annotations. If performance degradation is NOT an issue at the configured limit, raise the limit value using the CacheManager or Cache elements maxDepth attribute. For more information, see the Ehcache configuration documentation. (ObjectGraphWalker.java [tomcat-http-2])
  • WARN 2016-12-05 13:08:37,197 The configured limit of 1,000 object references was reached while attempting to calculate the size of the object graph. Severe performance degradation could occur if the sizing operation continues. This can be avoided by setting the CacheManger or Cache elements maxDepthExceededBehavior to “abort” or adding stop points with @IgnoreSizeOf annotations. If performance degradation is NOT an issue at the configured limit, raise the limit value using the CacheManager or Cache elements maxDepth attribute. For more information, see the Ehcache configuration documentation. (ObjectGraphWalker.java [tomcat-http-2])

etc….

Hi Olav,

this warning comes from a cache-related setting in Tomcat 8.5 having a quite low default value. You can adjust it by including this in tomcat/conf/context.xml:

The crash might come from something else.

Lars

···

On Mon, Dec 5, 2016 at 7:28 PM, Olav Poppe olav.poppe@me.com wrote:

Hi devs, we’re having som problems woth a 2.24 instance that crashes. This is what we find in the logs (below) - the warning repeats itself until tomcat crashes. Any advice?

Regards

Olav

  • INFO 2016-12-05 13:08:02,235 ‘lamin’ update org.hisp.dhis.program.ProgramInstance, uid: vACQtdeeQ11 (AuditLogUtil.java [tomcat-http-10])
  • WARN 2016-12-05 13:08:31,680 The configured limit of 1,000 object references was reached while attempting to calculate the size of the object graph. Severe performance degradation could occur if the sizing operation continues. This can be avoided by setting the CacheManger or Cache elements maxDepthExceededBehavior to “abort” or adding stop points with @IgnoreSizeOf annotations. If performance degradation is NOT an issue at the configured limit, raise the limit value using the CacheManager or Cache elements maxDepth attribute. For more information, see the Ehcache configuration documentation. (ObjectGraphWalker.java [tomcat-http-2])
  • WARN 2016-12-05 13:08:37,197 The configured limit of 1,000 object references was reached while attempting to calculate the size of the object graph. Severe performance degradation could occur if the sizing operation continues. This can be avoided by setting the CacheManger or Cache elements maxDepthExceededBehavior to “abort” or adding stop points with @IgnoreSizeOf annotations. If performance degradation is NOT an issue at the configured limit, raise the limit value using the CacheManager or Cache elements maxDepth attribute. For more information, see the Ehcache configuration documentation. (ObjectGraphWalker.java [tomcat-http-2])

etc….


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

Thanks Lars. Is that cacheMaxSize=“100000” an arbitrary example or a sensible default? (I am thinking here of setting the default on dhis2-tools instance)

···

On 6 December 2016 at 08:02, Lars Helge Øverland lars@dhis2.org wrote:

Hi Olav,

this warning comes from a cache-related setting in Tomcat 8.5 having a quite low default value. You can adjust it by including this in tomcat/conf/context.xml:

The crash might come from something else.

Lars


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

On Mon, Dec 5, 2016 at 7:28 PM, Olav Poppe olav.poppe@me.com wrote:

Hi devs, we’re having som problems woth a 2.24 instance that crashes. This is what we find in the logs (below) - the warning repeats itself until tomcat crashes. Any advice?

Regards

Olav

  • INFO 2016-12-05 13:08:02,235 ‘lamin’ update org.hisp.dhis.program.ProgramInstance, uid: vACQtdeeQ11 (AuditLogUtil.java [tomcat-http-10])
  • WARN 2016-12-05 13:08:31,680 The configured limit of 1,000 object references was reached while attempting to calculate the size of the object graph. Severe performance degradation could occur if the sizing operation continues. This can be avoided by setting the CacheManger or Cache elements maxDepthExceededBehavior to “abort” or adding stop points with @IgnoreSizeOf annotations. If performance degradation is NOT an issue at the configured limit, raise the limit value using the CacheManager or Cache elements maxDepth attribute. For more information, see the Ehcache configuration documentation. (ObjectGraphWalker.java [tomcat-http-2])
  • WARN 2016-12-05 13:08:37,197 The configured limit of 1,000 object references was reached while attempting to calculate the size of the object graph. Severe performance degradation could occur if the sizing operation continues. This can be avoided by setting the CacheManger or Cache elements maxDepthExceededBehavior to “abort” or adding stop points with @IgnoreSizeOf annotations. If performance degradation is NOT an issue at the configured limit, raise the limit value using the CacheManager or Cache elements maxDepth attribute. For more information, see the Ehcache configuration documentation. (ObjectGraphWalker.java [tomcat-http-2])

etc….


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org