[jbosscache-issues] [JBoss JIRA] Commented: (JBCACHE-1545) remove does not remove node when using optimistic locking and called on an instance which does not contain the node.

Tue Apr 6 11:07:38 EDT 2010

    [ https://jira.jboss.org/jira/browse/JBCACHE-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12524060#action_12524060 ] 

Aleksander Adamowski commented on JBCACHE-1545:
-----------------------------------------------

Any chance that this would be released as JBoss Cache 1.4.1.SP14?

> remove does not remove node when using optimistic locking and called on an instance which does not contain the node.
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1545
>                 URL: https://jira.jboss.org/jira/browse/JBCACHE-1545
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Replication
>    Affects Versions: 1.4.1.SP13
>            Reporter: Dennis Reed
>            Assignee: Galder Zamarreno
>             Fix For: 1.4.X
>
>         Attachments: jboss-cache-jdk50.jar, patch-v1.txt
>
>
> With optimistic locking, remove ( String fqn ), and remove ( String fgn, Object key ) do not remove from other cluster members if the node does not exist in the local cache.
> This can happen when using invalidation, or when the node has been evicted.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira