activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher L. Shannon (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AMQ-5546) selectorAware subscription cache replication
Date Mon, 06 Feb 2017 14:34:41 GMT

     [ https://issues.apache.org/jira/browse/AMQ-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Christopher L. Shannon closed AMQ-5546.
---------------------------------------
    Resolution: Won't Fix

LevelDB has been deprecated and is no longer supported.

> selectorAware subscription cache replication
> --------------------------------------------
>
>                 Key: AMQ-5546
>                 URL: https://issues.apache.org/jira/browse/AMQ-5546
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.10.0
>         Environment: ActiveMQ 5.10.0
> Replica Leveldb Cluster
>            Reporter: Pankaj Takawale
>              Labels: selector, virtualtopic
>
> AMQ Replica LevelDB cluster does not replicate VirtualTopic Subscriber's selector expression.
So on consumer disconnect followed by failover, new master does not have consumer's selector
expression. It causes consumer to miss messages published during its offline duration.
> Steps to reproduce:
> 1. consumer subscribes (JMSSelector filter)
> 2. producer publishes
> 3. consumer consumes
> 4. consumer disconnects (offline)
> 5. Activemq *failover* occurs (new master gets elected)
> 6. producer publishes
> 7. consumer reconnects ( missed messages during offline period)
> I poked around SelectorAware cache code. It persists selector cache to local filesystem,
that never gets replicated to slave nodes.
> Possible solution is to persists subscription info to leveldb, so that it gets replicated.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message