[BOOKKEEPER-441] InMemorySubscriptionManager should back up top2sub2seq before change it

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 4.2.0
• Fix Version/s: 4.2.0
• Component/s: hedwig-server
• Labels: patch

Environment

unix

• Assignee: Yixue Zhu
• Reporter: Yixue Zhu
• Created: 24/Oct/12 16:37
• Updated: 13/Feb/13 15:46
• Resolved: 26/Oct/12 10:13

Description

On topic loss, InMemorySubscriptionManager currently does not clear top2sub2seq. The intent is to allow readSubscription to get the information there. This introduce dependency outside the class, evidence is that general ReleaseOp has to use a boolean parameter which targets this implementation detail. Further, this prevents Acquire-topic to notify listeners (notifyFirstLocalSubscribe is not called) of first subscription to act appropriately.