Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2.0.0.BETA2, 2.0.0.GA
    • Component/s: None
    • Labels:
      None

      Description

      This is to supercede putFailFast() in JBC 1.x as well as the Option.FAIL_SILENTLY option, for Hibernate to use when doing a DB read and putting the contents into the cache.

      See forum link for details of this.

        Gliffy Diagrams

          Activity

          Hide
          manik Manik Surtani added a comment -

          Needs more discussion, moving to BETA2

          Show
          manik Manik Surtani added a comment - Needs more discussion, moving to BETA2
          Show
          manik Manik Surtani added a comment - http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheHibernateAlignment
          Hide
          manik Manik Surtani added a comment -

          Following the call we had with the HIbernate folk on 26 FEB 2007, here are the salient points wrt. putForExternalRead (PFER)

          • PFER only goes through if node does not exist; no-op otherwise
          • Force asynchronous mode for replication or invalidation to prevent any blocking
          • 0ms lock timeout to prevent any blocking here either. If this fails, PFER is a no-op
          • no to separate thread necessary, since we will be operating with a 0ms timeout, async replication and a no-op if the node exists. The only real chance of any blocking here is JGroups FC which is considered small enough a case.

          Existing points which still are valid from the wiki link above:

          • Suspend all ongoing TXs.
          • Quieter logging. Errors and the like that would otherwise raise alarm bells should be suppressed since this is a non-critical call.

          This serves as a "spec" for PFER and the basis for unit tests.

          Show
          manik Manik Surtani added a comment - Following the call we had with the HIbernate folk on 26 FEB 2007, here are the salient points wrt. putForExternalRead (PFER) PFER only goes through if node does not exist; no-op otherwise Force asynchronous mode for replication or invalidation to prevent any blocking 0ms lock timeout to prevent any blocking here either. If this fails, PFER is a no-op no to separate thread necessary, since we will be operating with a 0ms timeout, async replication and a no-op if the node exists. The only real chance of any blocking here is JGroups FC which is considered small enough a case. Existing points which still are valid from the wiki link above: Suspend all ongoing TXs. Quieter logging. Errors and the like that would otherwise raise alarm bells should be suppressed since this is a non-critical call. This serves as a "spec" for PFER and the basis for unit tests.

            People

            • Assignee:
              manik Manik Surtani
              Reporter:
              manik Manik Surtani
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development