Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-3010

HHH-4517 Hibernate/JBC integration doesn't property handle Entity/CollectionRegionAccessStrategy evict(Object)

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: EAP 5.0.0.CR4 (FCS and BETA2), EAP 5.0.0.CR5, EAP 5.0.0
    • Fix Version/s: TBD EAP 5
    • Component/s: Hibernate
    • Labels:
      None
    • Affects:
      Release Notes
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      This method is invoked as a result of the application using the SessionFactory.evictXXX(..., Serializable id) API. Applications using this API should recognize that calls to it may block waiting for other transactions to complete with a JBoss Cache based Second Level Cache.

      Further, such calls that occur in the middle of a transaction will hold locks until the transaction commits and will not update other nodes until the transaction commits. If this is a problem, it may be helpful to do the eviction before the transaction begins or after it commits.

      Show
      This method is invoked as a result of the application using the SessionFactory.evictXXX(..., Serializable id) API. Applications using this API should recognize that calls to it may block waiting for other transactions to complete with a JBoss Cache based Second Level Cache. Further, such calls that occur in the middle of a transaction will hold locks until the transaction commits and will not update other nodes until the transaction commits. If this is a problem, it may be helpful to do the eviction before the transaction begins or after it commits.
    • Release Notes Docs Status:
      Not Required

      Description

      The API contract for EntityRegionAccessStrategy.evict(Object) and CollectionRegionAccessStrategy.evict(Object) states that an item should be forcibly evicted from the cache immediately, without regard for transaction isolation. The Hibernate/JBoss Cache integration does not implement this properly because the JBC removeNode() calls it makes do not deal with transactional issues.

      http://opensource.atlassian.com/projects/hibernate/browse/HHH-4517

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  stliu Strong Liu
                  Reporter:
                  stliu Strong Liu
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: