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

Auto-disable expiration/eviction configuration from distributed web/ejb caches

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 11.0.0.Beta1
    • 11.0.0.Alpha1
    • Clustering
    • None
    • Hide

      Set
      <cache-container name="ejb" aliases="sfsb" default-cache="passivation" module="org.wildfly.clustering.ejb.infinispan">
      <local-cache name="passivation">
      <locking isolation="REPEATABLE_READ"/>
      <transaction mode="BATCH"/>
      <eviction strategy="LRU" max-entries="100"/>
      <expiration max-idle="30000"/>
      <file-store passivation="true" purge="false"/>
      </local-cache>

      Hit a EJB that uses this cache and wait for the timeout to occur, NoSuchEJBException is thrown.

      Show
      Set <cache-container name="ejb" aliases="sfsb" default-cache="passivation" module="org.wildfly.clustering.ejb.infinispan"> <local-cache name="passivation"> <locking isolation="REPEATABLE_READ"/> <transaction mode="BATCH"/> <eviction strategy="LRU" max-entries="100"/> <expiration max-idle="30000"/> <file-store passivation="true" purge="false"/> </local-cache> Hit a EJB that uses this cache and wait for the timeout to occur, NoSuchEJBException is thrown.
    • Hide

      Use @StatefulTimeout instead of expiration.

      Show
      Use @StatefulTimeout instead of expiration.

    Description

      Setting expiration for cache-container ejb, does not trigger the @PreDestroy method.
      Request to remove the expiration configuration for internal ISPN we should have at least a WARN message that expiration for SFSB is not working.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-10582 (7.1.0) remove expiration configuration from the internal ispn subsystem to prevent from false configurations

          • 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

          Activity

            People

              pferraro@redhat.com Paul Ferraro
              pferraro@redhat.com Paul Ferraro
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: