Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-32806

Excessive WARNINGS from ehcache

XMLWordPrintable

      https://answers.atlassian.com/questions/244282/lots-of-confluence-ehcache-sizeof-warnings

      2013-12-17 15:09:56,992 WARN [pool-1-thread-1] [ehcache.pool.impl.DefaultSizeOfEngine] sizeOf key type: java.lang.Long
2013-12-17 15:09:56,992 WARN [pool-1-thread-1] [ehcache.pool.impl.DefaultSizeOfEngine] sizeOf key: 1606064
2013-12-17 15:09:56,993 WARN [pool-1-thread-1] [ehcache.pool.impl.DefaultSizeOfEngine] sizeOf value type: net.sf.ehcache.Element

      Seems like many users are seeing this, including me.

            [CONFSERVER-32806] Excessive WARNINGS from ehcache

            Martin Kukielka added a comment -

            Here also occuring massively in Confluence wiki 5.4.3

            Martin Kukielka added a comment - Here also occuring massively in Confluence wiki 5.4.3

            Jens Kasperek (Bosch GmbH) added a comment -

            Still a bug on Conf 5.5.6 - please reopen this bug report!!!

            Jens Kasperek (Bosch GmbH) added a comment - Still a bug on Conf 5.5.6 - please reopen this bug report!!!

            Julia Wester added a comment -

            http://www.ksmpartners.com/2013/07/custom-ehcache-sizing-engines/

            Julia Wester added a comment - http://www.ksmpartners.com/2013/07/custom-ehcache-sizing-engines/

            Julia Wester added a comment -

            +1, this is not resolved. I see these in Confluence 5.4.4 as well. @mansour, how can we get someone to reopen and investigate?

            Julia Wester added a comment - +1, this is not resolved. I see these in Confluence 5.4.4 as well. @mansour, how can we get someone to reopen and investigate?

            Jonas Andersson added a comment -

            Still a bug in 5.5 too, not sure why this issue was closed.

            Jonas Andersson added a comment - Still a bug in 5.5 too, not sure why this issue was closed.

            Marc Schäpers added a comment -

            The bug is still a problem - Confluence version 5.5.2

            Marc Schäpers added a comment - The bug is still a problem - Confluence version 5.5.2

            Arya Banerjee added a comment -

            +1 for Confluence 5.4.4. We are still facing this warning and there is a huge performance issue while loading the lage. Can anybody please suggest us a solution to resolve this?

            Arya Banerjee added a comment - +1 for Confluence 5.4.4. We are still facing this warning and there is a huge performance issue while loading the lage. Can anybody please suggest us a solution to resolve this?

            Srinivas Patruni added a comment -

            +1 for 5.4.2 and no net.sf.ehcache.pool.impl.DefaultSizeOfEngine parameter in logging and profiling section

            2014-08-22 23:02:17,153 WARN [pool-1-thread-1] [ehcache.pool.impl.DefaultSizeOfEngine] sizeOf value type: net.sf.ehcache.Element
2014-08-22 23:02:17,154 WARN [pool-1-thread-1] [ehcache.pool.impl.DefaultSizeOfEngine] sizeOf value: [ key = 41462129, value=Item{version=null,freshTimestamp=5770203630002187,value type=[Ljava.io.Serializable;}, version=1, hitCount=1, CreationTime = 1408741120606, LastAccessTime = 1408743015866 ]
2014-08-22 23:02:17,155 WARN [pool-1-thread-1] [ehcache.pool.impl.DefaultSizeOfEngine] sizeOf container: net.sf.ehcache.store.chm.SelectableConcurrentHashMap$HashEntry@31fffbf0
2014-08-22 23:02:17,158 WARN [pool-1-thread-1] [ehcache.pool.impl.DefaultSizeOfEngine] sizeOf The configured limit of 100 object references was reached while attempting to calculate the size of the object graph. This can be avoided by adding stop points with @IgnoreSizeOf annotations. Since the CacheManger or Cache <sizeOfPolicy> elements maxDepthExceededBehavior is set to "abort", the sizing operation has stopped and the reported cache size is not accurate. If performance degradation is NOT an issue at the configured limit, raise the limit value using the CacheManager or Cache <sizeOfPolicy> elements maxDepth attribute. For more information, see the Ehcache configuration documentation.
2014-08-22 23:02:17,159 WARN [pool-1-thread-1] [ehcache.pool.impl.DefaultSizeOfEngine] sizeOf key type: java.lang.Long
2014-08-22 23:02:17,160 WARN [pool-1-thread-1] [ehcache.pool.impl.DefaultSizeOfEngine] sizeOf key: 48936640

            Srinivas Patruni added a comment - +1 for 5.4.2 and no net.sf.ehcache.pool.impl.DefaultSizeOfEngine parameter in logging and profiling section 2014-08-22 23:02:17,153 WARN [pool-1-thread-1] [ehcache.pool.impl.DefaultSizeOfEngine] sizeOf value type: net.sf.ehcache.Element 2014-08-22 23:02:17,154 WARN [pool-1-thread-1] [ehcache.pool.impl.DefaultSizeOfEngine] sizeOf value: [ key = 41462129, value=Item{version=null,freshTimestamp=5770203630002187,value type=[Ljava.io.Serializable;}, version=1, hitCount=1, CreationTime = 1408741120606, LastAccessTime = 1408743015866 ] 2014-08-22 23:02:17,155 WARN [pool-1-thread-1] [ehcache.pool.impl.DefaultSizeOfEngine] sizeOf container: net.sf.ehcache.store.chm.SelectableConcurrentHashMap$HashEntry@31fffbf0 2014-08-22 23:02:17,158 WARN [pool-1-thread-1] [ehcache.pool.impl.DefaultSizeOfEngine] sizeOf The configured limit of 100 object references was reached while attempting to calculate the size of the object graph. This can be avoided by adding stop points with @IgnoreSizeOf annotations. Since the CacheManger or Cache <sizeOfPolicy> elements maxDepthExceededBehavior is set to "abort", the sizing operation has stopped and the reported cache size is not accurate. If performance degradation is NOT an issue at the configured limit, raise the limit value using the CacheManager or Cache <sizeOfPolicy> elements maxDepth attribute. For more information, see the Ehcache configuration documentation. 2014-08-22 23:02:17,159 WARN [pool-1-thread-1] [ehcache.pool.impl.DefaultSizeOfEngine] sizeOf key type: java.lang.Long 2014-08-22 23:02:17,160 WARN [pool-1-thread-1] [ehcache.pool.impl.DefaultSizeOfEngine] sizeOf key: 48936640

            Hans-Peter Geier added a comment -

            +1 for 5.4.4 still has this problem. Atlassian should update the affects Version(s).
            And
            +1 for net.sf.ehcache.pool.impl.DefaultSizeOfEngine parameter does not exist in Confluence 5.4.4,
            therefore your workaround cannot be applied
            and
            +1 for "no custom log4j.properties file" (in case you want to ask me this)

            What are the impact of these warnings? Are they just filling the log file (then I would not care), or are they performance-related?

            Hans-Peter Geier added a comment - +1 for 5.4.4 still has this problem. Atlassian should update the affects Version(s). And +1 for net.sf.ehcache.pool.impl.DefaultSizeOfEngine parameter does not exist in Confluence 5.4.4, therefore your workaround cannot be applied and +1 for "no custom log4j.properties file" (in case you want to ask me this) What are the impact of these warnings? Are they just filling the log file (then I would not care), or are they performance-related?

            Sumit Kumar added a comment - - edited

            error in Confluence 5.4.2

            2014-04-23 06:06:55,454 WARN [pool-1-thread-1] [ehcache.pool.impl.DefaultSizeOfEngine] sizeOf key type: java.lang.Long
2014-04-23 06:06:55,455 WARN [pool-1-thread-1] [ehcache.pool.impl.DefaultSizeOfEngine] sizeOf key: 47771917
2014-04-23 06:06:55,455 WARN [pool-1-thread-1] [ehcache.pool.impl.DefaultSizeOfEngine] sizeOf value type: net.sf.ehcache.Element
2014-04-23 06:06:55,456 WARN [pool-1-thread-1] [ehcache.pool.impl.DefaultSizeOfEngine] sizeOf value: [ key = 47771917, value=Item{version=null,freshTimestamp=5727135634153479,value type=[Ljava.io.Serializable;}, version=1, hitCount=3, CreationTime = 1398226473182, LastAccessTime = 1398226505436 ]
2014-04-23 06:06:55,457 WARN [pool-1-thread-1] [ehcache.pool.impl.DefaultSizeOfEngine] sizeOf container: net.sf.ehcache.store.chm.SelectableConcurrentHashMap$HashEntry@5d816f73

            Sumit Kumar added a comment - - edited error in Confluence 5.4.2 2014-04-23 06:06:55,454 WARN [pool-1-thread-1] [ehcache.pool.impl.DefaultSizeOfEngine] sizeOf key type: java.lang. Long 2014-04-23 06:06:55,455 WARN [pool-1-thread-1] [ehcache.pool.impl.DefaultSizeOfEngine] sizeOf key: 47771917 2014-04-23 06:06:55,455 WARN [pool-1-thread-1] [ehcache.pool.impl.DefaultSizeOfEngine] sizeOf value type: net.sf.ehcache.Element 2014-04-23 06:06:55,456 WARN [pool-1-thread-1] [ehcache.pool.impl.DefaultSizeOfEngine] sizeOf value: [ key = 47771917, value=Item{version= null ,freshTimestamp=5727135634153479,value type=[Ljava.io.Serializable;}, version=1, hitCount=3, CreationTime = 1398226473182, LastAccessTime = 1398226505436 ] 2014-04-23 06:06:55,457 WARN [pool-1-thread-1] [ehcache.pool.impl.DefaultSizeOfEngine] sizeOf container: net.sf.ehcache.store.chm.SelectableConcurrentHashMap$HashEntry@5d816f73

              drizzuto David Rizzuto
              a38518e05741 David Yu
              Affected customers:
              9 This affects my team
              Watchers:
              53 Start watching this issue

                Created:
                Updated:
                Resolved: