[
https://issues.jboss.org/browse/ISPN-4438?page=com.atlassian.jira.plugin....
]
Martin Gencur resolved ISPN-4438.
---------------------------------
Resolution: Deferred
The root cause is following:
When a HotRod client first reads a key from a node which is not the owner, the value is
retrieved from another node. As part of this process, the value is marhalled on the owner
node and sent back to the requester where it is stored in L1 as it is - marshalled. Then a
copy of the entry is unmarshalled and returned back to the client. When the key is
requested second time the marshalled entry is taken from L1 cache but is marshalled AGAIN
and returned to the client.
This only happens when data is requested by HotRod client. It does not happen when
requested by a local thread from an embedded cache or via REST.
L1 cache does not make much sense when using HotRod client because the client knows which
node is the owner and requests data from that node directly (no use of L1) so this is not
a bug.
Entry is not properly unmarshalled in compatibility mode when L1
enabled
------------------------------------------------------------------------
Key: ISPN-4438
URL:
https://issues.jboss.org/browse/ISPN-4438
Project: Infinispan
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 7.0.0.Alpha4
Reporter: Martin Gencur
Assignee: Martin Gencur
Fix For: 7.0.0.Alpha5
When a distributed cache is used together with compatibility mode and L1 is enabled. The
entry being returned to the client is not unmarshalled when it is found in the L1 cache.
Unmarshalling works fine if the entry is retrieved from a remote node (not found in L1).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)