Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.1.8
    • Fix Version/s: None
    • Component/s: - Components: Avalon
    • Labels:
      None
    • Environment:
      Operating System: other
      Platform: Other

      Description

      I've seen the discussion about the Sleepycat license, and realize this can't be
      a part of the distribution, but thought someone might find it useful. It is a
      bit raw and needs some polishing. Portions of this have been shamelessly cut
      and pasted from JCSDefaultStore. I haven't been brave enough to use this in
      production, but on staging servers it has been working nicely.

        Activity

        Hide
        Charles Yates added a comment -
        Created an attachment (id=11845)
        source code
        Show
        Charles Yates added a comment - Created an attachment (id=11845) source code
        Hide
        Charles Yates added a comment -
        Created an attachment (id=11986)
        new version
        Show
        Charles Yates added a comment - Created an attachment (id=11986) new version
        Hide
        Charles Yates added a comment -
        Preloading the memory cache is a cpu hog on startup, the new version has that
        step removed. So far, I have not encountered any problems with this store
        implementation. I am still not brave enough to use it on our production site
        though.
        Show
        Charles Yates added a comment - Preloading the memory cache is a cpu hog on startup, the new version has that step removed. So far, I have not encountered any problems with this store implementation. I am still not brave enough to use it on our production site though.
        Hide
        Charles Yates added a comment -
        After some consultations with Sleepycat I have determined that the cpu hogging I
        had noted was not due to the cache preload, but happened when the db environment
        wasn't closed properly, a consequence of 'other than normal' servlet container
        shutdown. In that case, a subsequent restart involves a recovery process that
        is causing the db to go into a recovery process the next time it is started.
        Show
        Charles Yates added a comment - After some consultations with Sleepycat I have determined that the cpu hogging I had noted was not due to the cache preload, but happened when the db environment wasn't closed properly, a consequence of 'other than normal' servlet container shutdown. In that case, a subsequent restart involves a recovery process that is causing the db to go into a recovery process the next time it is started.

          People

          • Assignee:
            Unassigned
            Reporter:
            Charles Yates
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development