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

(7.1.0) remove expiration configuration from the internal ispn subsystem to prevent from false configurations

XMLWordPrintable

    • Hide

      Use @StatefulTimeout instead of expiration.

      Show
      Use @StatefulTimeout instead of expiration.
    • 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.

      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.

              pferraro@redhat.com Paul Ferraro
              rhn-support-tmiyargi Teresa Miyar Gil (Inactive)
              Michal Vinkler Michal Vinkler
              Michal Vinkler Michal Vinkler
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: