Uploaded image for project: 'OpenJPA'
  1. OpenJPA
  2. OPENJPA-1328

Move cacheable class configuration to ClassMetaData

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 1.2.0, 1.2.1
    • 1.0.4, 1.2.2, 1.3.0, 2.0.0-beta
    • datacache
    • None

    Description

      I'm proposing to move the cacheable class configuration processing from the datacache classes to ClassMetaData. The feature, introduced in OPENJPA-1045, effectively works by returning null for ClassMetaData.getDataCacheName(), where classes which should not be cached return null, otherwise the name of the datacache they may be cached by is returned.

      THe problem is that some third party datacache plugins are not reentrant, and the existing ClassMetaData.isCacheable() makes use of the method call getRepository().getConfiguration().getDataCacheManagerInstance(). This invokes the initialization of the datacache, which may result in further initialization/copying of CMD objects, which reenter the isCacheable() method. If a third party datacache plugin is not reentrant safe, this can cause a failure in the form of Exceptions or hung threads.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            mikedd Michael Dick
            fyrewyld Jody Grassel
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment