[
https://issues.apache.org/jira/browse/AMQ-5153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14512216#comment-14512216
]
Brian Davis commented on AMQ-5153:
----------------------------------
I did not get enough time to go through your test and change it to show the
issue. I did go through what I did before and reproduced the bug. I also
think I know what is wrong with your test.
If you do the steps I stated on a broker that you can restart (kill the process
and bring back a new process) it will show the bug. I did my test through the
web console and the bug is still there on 5.11.1. The key is restarting the
broker. I believe that is also the issue with your test. You never get a new
broker you reuse a broker, stopping and starting it. My guess is the
LevelDBPersistentAdapter probably does not get rid of state on the stop of a
broker and reuses that state on a start.
Hope this helps.
> LevelDB does not store subscribedDestination for durable subscriptions
> ----------------------------------------------------------------------
>
> Key: AMQ-5153
> URL: https://issues.apache.org/jira/browse/AMQ-5153
> Project: ActiveMQ
> Issue Type: Bug
> Components: activemq-leveldb-store
> Affects Versions: 5.9.1
> Reporter: Brian Davis
>
> LevelDB store does not save the subscribedDestination of the SubscriptionInfo
> for a durable subscription. This is important because when a restart happens
> you have no clue if this durable subscription goes with the topic or to a
> different topic (because of wildcarding).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
