[jboss-jira] [JBoss JIRA] Reopened: (JBCLUSTER-238) CacheListener does not properly handle notifications from buddy backup "xxx:DEAD" Fqns

[Brian Stansberry (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBCLUSTER-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry reopened JBCLUSTER-238:
----------------------------------------



Reopening as failover testing found flaws in initial fix.

> CacheListener does not properly handle notifications from buddy backup "xxx:DEAD" Fqns
> --------------------------------------------------------------------------------------
>
>                 Key: JBCLUSTER-238
>                 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-238
>             Project: JBoss Clustering
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: HA-Server-Cache-JBC
>    Affects Versions: HA-Server-Cache-SPI 2.0.0.GA
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: HA-Server-Cache-JBC 2.0.1.GA 
>
>
> The logic in CacheListener that determines if a notification is "interesting" assumes a fixed number of levels in the tree. The JBC behavior of moving dead node backups from "/BUDDY_BACKUP/xxx/JSESSION" to "/BUDDY_BACKUP/xxx:DEAD/#/JSESSION/" breaks this logic.
> One result is backup managers don't realize sessions are being updated and may try to expire them prematurely.

-- 
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