Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

CachePut on Infinispan Cache throws a warning "REMOVE" could result in inconsistency

Description

If you make a CachePut on a Cache, that was linked to a remote InfiniSpan, the log of Infinispan fill up with lot of warnings about this actions.

It seems to be related to latest Extension version of "Infinispan Cache (Remote)" version 8.2.3.21-SNAPSHOT

//2018-04-09 12:35:31,941 WARN [org.infinispan.server.hotrod.Decoder2x] (HotRod-ServerWorker-5-2) ISPN006011: Operation 'REMOVE' forced to return previous value should be used on transactional caches, otherwise data inconsistency issues could arise under failure situations
{/code}

I don´t know if this could become an critical issue.

Environment

None

Activity

Show:

Alexander Diedler 18 October 2018 at 18:46

It seems that this option help to avoid the error message.

Michael Offner 10 October 2018 at 05:54

to address this ticket for the current sprint, we need some input.

Alexander Diedler 18 September 2018 at 07:28

Hello Michi, I will come back to you, but I am pretty sure, we use this option already.

Michael Offner 14 September 2018 at 16:15

can you please check if that solves the issue

Michael Offner 14 September 2018 at 16:14

Solution seem to be with the server, so the INfinispan cache itself:

Resolution
To remove these messages from logs, enable transactions on the JDG cache on the server side in your configuration.
Change the transaction mode to NON-XA in your cache :

Root Cause
For each cache that uses operations which requires the cache data to be always consistent across the cluster (such as conditional operations)
then the transaction mode should be changed from NONE to NON_XA.

Source
https://access.redhat.com/solutions/3191172

Done

Details

Assignee

Reporter

Priority

Labels

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Sprint

Affects versions

Created 11 April 2018 at 12:29
Updated 13 June 2023 at 07:41
Resolved 18 March 2019 at 16:33