[infinispan-issues] [JBoss JIRA] (ISPN-3048) Eviction needs to be transactional
RH Bugzilla Integration (JIRA)
jira-events at lists.jboss.org
Thu Oct 10 15:15:03 EDT 2013
[ https://issues.jboss.org/browse/ISPN-3048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12813250#comment-12813250 ]
RH Bugzilla Integration commented on ISPN-3048:
-----------------------------------------------
Dominik Pospisil <dpospisi at redhat.com> made a comment on [bug 1017827|https://bugzilla.redhat.com/show_bug.cgi?id=1017827]
The issue affects EAP's internal caches (not JBossCache based portal caches) - mainly web session and SFSB caches.
To disable the passivation user needs to remove <file-store/> element from cahce config in the server profile configuration.
E.g. to disable web session cache passivation the following fragment of standalone/configuration/standalone-ha.xml
<cache-container name="web" aliases="standard-session-cache" default-cache="repl" module="org.jboss.as.clustering.web.infinispan">
<transport lock-timeout="60000"/>
<replicated-cache name="repl" mode="ASYNC" batching="true">
<file-store/>
</replicated-cache>
<replicated-cache name="sso" mode="SYNC" batching="true"/>
<distributed-cache name="dist" mode="ASYNC" batching="true" l1-lifespan="0">
<file-store/>
</distributed-cache>
</cache-container>
should be changed to:
<cache-container name="web" aliases="standard-session-cache" default-cache="repl" module="org.jboss.as.clustering.web.infinispan">
<transport lock-timeout="60000"/>
<replicated-cache name="repl" mode="ASYNC" batching="true">
<!-- <file-store/> -->
</replicated-cache>
<replicated-cache name="sso" mode="SYNC" batching="true"/>
<distributed-cache name="dist" mode="ASYNC" batching="true" l1-lifespan="0">
<!-- <file-store/> -->
</distributed-cache>
</cache-container>
> Eviction needs to be transactional
> ----------------------------------
>
> Key: ISPN-3048
> URL: https://issues.jboss.org/browse/ISPN-3048
> Project: Infinispan
> Issue Type: Bug
> Components: Eviction
> Affects Versions: 5.3.0.Alpha1
> Reporter: Paul Ferraro
> Assignee: William Burns
> Priority: Critical
>
> Currently, Infinispan eviction is non-transactional. This makes Infinispan's eviction manager virtually unusable, since non-transactional eviction can cause phantom reads and data loss because it violates the isolation of concurrent transactions. This is especially problematic when using a passivation-enabled cache store. In this case, a cache eviction/passivation can cause a concurrently executed cache retrieval to return null - even though the act of passivation does not change the data - it only changes where it is stored.
> We work around this in the AS by performing eviction manually, using pessimistic locking in combination with eager lock acquisition prior to eviction. This is unfortunate, since it prevents me from leveraging Infinispan's build-in eviction strategies.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list