Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: 0.20 Larks
    • Fix Version/s: 1.5 Larks
    • Labels:
      None
    • Sprint:
      1.3 Larks, 1.4 Larks, 1.5 Larks

      Description

      We have hell a lot of such warnings in logs:

      A soft-locked cache entry was expired by the underlying Ehcache. If this happens regularly you should consider increasing the cache timeouts and/or capacity limits
      2012-12-13 21:11:56,870 [WARN ][http-8080-23    ][he.hibernate.strategy.AbstractReadWriteEhcacheAccessStrategy] - Cache org.jtalks.jcommune.model.entity.Topic Key org.jtalks.jcommune.model.entity.Topic#31554 Lockable : null

        Attachments

          Activity

          Hide
          evgeny.kapinos Evgeny Kapinos added a comment - - edited

          Stanislav Bashkyrtsev Could you suggest how to reproduce this warning. Even on which page? I can generate some big data, but I don't now where to start.

          I try to edit encache.xml and decrease maxElementsInMemory="1" value on <defaultCache> and <cache name="org.hibernate.cache.StandardQueryCache" ...> tags. Try to load http://localhost:8080/jcommune/branches/1 with 9 topics. But I didn't reproduce this warning.

          Show
          evgeny.kapinos Evgeny Kapinos added a comment - - edited Stanislav Bashkyrtsev Could you suggest how to reproduce this warning. Even on which page? I can generate some big data, but I don't now where to start. I try to edit encache.xml and decrease maxElementsInMemory="1" value on <defaultCache> and <cache name="org.hibernate.cache.StandardQueryCache" ...> tags. Try to load http://localhost:8080/jcommune/branches/1 with 9 topics. But I didn't reproduce this warning.
          Hide
          ctapobep Stanislav Bashkyrtsev added a comment -

          I don't know what page, from the message I'd think this happens because the timeout is too small and the amount of objects is pretty high.

          Show
          ctapobep Stanislav Bashkyrtsev added a comment - I don't know what page, from the message I'd think this happens because the timeout is too small and the amount of objects is pretty high.
          Hide
          ctapobep Stanislav Bashkyrtsev added a comment -

          I can provide you with javatalks database if you need big amount of records.

          Show
          ctapobep Stanislav Bashkyrtsev added a comment - I can provide you with javatalks database if you need big amount of records.
          Hide
          ctapobep Stanislav Bashkyrtsev added a comment -

          Create a separate branch jc1207.ehcache-warnings for corrections.

          Show
          ctapobep Stanislav Bashkyrtsev added a comment - Create a separate branch jc1207.ehcache-warnings for corrections.
          Hide
          ctapobep Stanislav Bashkyrtsev added a comment -

          We have the same config on UAT and we don't have these warnings. Did you find out why this message may appear? At least from reading code which logs this.

          Show
          ctapobep Stanislav Bashkyrtsev added a comment - We have the same config on UAT and we don't have these warnings. Did you find out why this message may appear? At least from reading code which logs this.
          Hide
          lamao Vyacheslav Mishcheryakov added a comment - - edited

          we have identical ehcache.xml on UAT and PREPROD. From what other people tell this warning may appear when cache size is too low for current data and some item is being evicted from cache. But I am not able to reproduce it even with maxElementsInMemory=1.
          Also I didn't find such warning in PREPROD logs.

          Show
          lamao Vyacheslav Mishcheryakov added a comment - - edited we have identical ehcache.xml on UAT and PREPROD. From what other people tell this warning may appear when cache size is too low for current data and some item is being evicted from cache. But I am not able to reproduce it even with maxElementsInMemory=1. Also I didn't find such warning in PREPROD logs.
          Hide
          ctapobep Stanislav Bashkyrtsev added a comment -

          Don't see these logs in PROD as well now, closing it.

          Show
          ctapobep Stanislav Bashkyrtsev added a comment - Don't see these logs in PROD as well now, closing it.

            People

            • Assignee:
              lamao Vyacheslav Mishcheryakov
              Reporter:
              ctapobep Stanislav Bashkyrtsev
            • Votes:
              0 Vote for this issue
              Watchers:
              Start watching this issue

              Dates

              • Due:
                Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 13h
                13h

                  Structure Helper Panel