Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-7628

Allow to use an Infinispan cache as EJB timer store

    XMLWordPrintable

Details

    Description

      EJB subsystem allows to configure a datanase datasource to use as a store for persistent timers.

      I miss the option to use an Infinispan cache, that could even be configured as the default store out of the box. This is something Payara is already offering with Hazelcast (https://payara.gitbooks.io/payara-server/content/documentation/extended-documentation/alternate-store-for-ejb-timers.html).

      Attachments

        Issue Links

          blocks

          Task - Represents a small unit of work that is not end-user facing. WFLY-16270 Modify EJB timer quickstart to demonstrate distributed EJB timers.

          • 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
          causes

          Bug - A problem that impairs or prevents the functions of the product. HAL-1947 Configuration -> EJB -> Services -> timer reset button display error pop-up notification

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved
          is blocked by

          Feature Request - Feature requests from customers and/or users WFLY-14953 Create distributable-ejb subsystem

          • 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
          is duplicated by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) WFLY-16331 TimerServiceResource locking performance improvement

          • 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.
          • Resolved
          is related to

          Sub-task - The sub-task of the issue WFLY-16781 Allow use of ProtoStream for marshalling timeout context of a distributed timer.

          • 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

          Feature Request - Feature requests from customers and/or users WFLY-12733 EJB Timers: Forcing refresh timers in a database-data-store in a clustered environment

          • 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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-24863 OpenShift - High frequency distributed timer fail-over is failing sometimes

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. WFWIP-458 [WFLY-7628] Bootable JAR - Wrong configuration when using ejb and ejb-dist-cache layers

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              pferraro@redhat.com Paul Ferraro
              ggam_jira Guillermo González de Agüero (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: