Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-8221

[GSS] (7.0.z) race condition between the start of the custom cache configurationservice and the cache creation by the region factory

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.0.5.CR1, 7.0.5.GA
    • 7.0.3.GA, 7.1.0.DR10
    • JPA/Hibernate
    • None
    • EAP 7.0.5

    Description

      The behavior EAP 7.1 is not completely correct as without the requisite deployment dependencies, there is a race condition between the start of the custom cache configuration service and the cache creation by the region factory.

      See JBEAP-8219 for context

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-8220 [GSS](7.1.0) race condition between the start of the custom cache configurationservice and the cache creation by the region factory

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          incorporates

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-8220 [GSS](7.1.0) race condition between the start of the custom cache configurationservice and the cache creation by the region factory

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-8219 [GSS] (7.0.z) Unable to reference a specific cache configured in standalone*.xml or domain*.xml

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          links to

          Web Link Red Hat Knowledge Base

          Activity

            People

              pferraro@redhat.com Paul Ferraro
              rhn-support-sfikes Stephen Fikes (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: