Package org.apache.activemq.store
Interface TopicReferenceStore
- All Superinterfaces:
MessageStore,ReferenceStore,org.apache.activemq.Service,TopicMessageStore
A MessageStore for durable topic subscriptions
-
Nested Class Summary
Nested classes/interfaces inherited from interface org.apache.activemq.store.MessageStore
MessageStore.StoreTypeNested classes/interfaces inherited from interface org.apache.activemq.store.ReferenceStore
ReferenceStore.ReferenceData -
Method Summary
Modifier and TypeMethodDescriptionbooleanacknowledgeReference(ConnectionContext context, String clientId, String subscriptionName, org.apache.activemq.command.MessageId messageId) Removes the last acknowledged messgeID for the given subscription so that we can recover and commence dispatching messages from the last checkpoint N.B. - all messages previous to this one for a given subscriber should also be acknowledgedvoidaddSubsciption(org.apache.activemq.command.SubscriptionInfo subscriptionInfo, boolean retroactive) Inserts the subscriber info due to a subscription changevoiddeleteSubscription(String clientId, String subscriptionName) org.apache.activemq.command.SubscriptionInfo[]Lists all the durable subscriptions for a given destination.intgetMessageCount(String clientId, String subscriberName) Get the number of messages ready to deliver from the store to a durable subscriberorg.apache.activemq.command.SubscriptionInfolookupSubscription(String clientId, String subscriptionName) Finds the subscriber entry for the given consumer infovoidrecoverNextMessages(String clientId, String subscriptionName, int maxReturned, MessageRecoveryListener listener) For an active subscription - retrieve messages from the store for the subscriber after the lastMessageId messageIdvoidrecoverSubscription(String clientId, String subscriptionName, MessageRecoveryListener listener) For the new subscription find the last acknowledged message ID and then find any new messages since then and dispatch them to the subscription.voidresetBatching(String clientId, String subscriptionName) A hint to the Store to reset any batching state for a durable subsriberMethods inherited from interface org.apache.activemq.store.MessageStore
addMessage, addMessage, asyncAddQueueMessage, asyncAddQueueMessage, asyncAddTopicMessage, asyncAddTopicMessage, dispose, getDestination, getMessage, getMessageCount, getMessageSize, getMessageStoreStatistics, getType, isEmpty, isPrioritizedMessages, recover, recoverMessages, recoverNextMessages, registerIndexListener, removeAllMessages, removeAsyncMessage, removeMessage, resetBatching, setMemoryUsage, setPrioritizedMessages, updateMessageMethods inherited from interface org.apache.activemq.store.ReferenceStore
addMessageReference, getMessageReference, getStoreLock, setBatch, supportsExternalBatchControlMethods inherited from interface org.apache.activemq.Service
start, stopMethods inherited from interface org.apache.activemq.store.TopicMessageStore
acknowledge, addSubscription, getMessageSize, getMessageStoreSubStatistics, recoverExpired
-
Method Details
-
acknowledgeReference
boolean acknowledgeReference(ConnectionContext context, String clientId, String subscriptionName, org.apache.activemq.command.MessageId messageId) throws IOException Removes the last acknowledged messgeID for the given subscription so that we can recover and commence dispatching messages from the last checkpoint N.B. - all messages previous to this one for a given subscriber should also be acknowledged- Parameters:
context-clientId-subscriptionName-messageId-- Returns:
- true if there are no more references to the message - or the message is null
- Throws:
IOException
-
deleteSubscription
- Specified by:
deleteSubscriptionin interfaceTopicMessageStore- Parameters:
clientId-subscriptionName-- Throws:
IOExceptionjakarta.jms.JMSException
-
recoverSubscription
void recoverSubscription(String clientId, String subscriptionName, MessageRecoveryListener listener) throws Exception For the new subscription find the last acknowledged message ID and then find any new messages since then and dispatch them to the subscription. e.g. if we dispatched some messages to a new durable topic subscriber, then went down before acknowledging any messages, we need to know the correct point from which to recover from.- Specified by:
recoverSubscriptionin interfaceTopicMessageStore- Parameters:
clientId-subscriptionName-listener-- Throws:
Exception
-
recoverNextMessages
void recoverNextMessages(String clientId, String subscriptionName, int maxReturned, MessageRecoveryListener listener) throws Exception For an active subscription - retrieve messages from the store for the subscriber after the lastMessageId messageId- Specified by:
recoverNextMessagesin interfaceTopicMessageStore- Parameters:
clientId-subscriptionName-maxReturned-listener-- Throws:
Exception
-
resetBatching
A hint to the Store to reset any batching state for a durable subsriber- Specified by:
resetBatchingin interfaceTopicMessageStore- Parameters:
clientId-subscriptionName-
-
getMessageCount
Get the number of messages ready to deliver from the store to a durable subscriber- Specified by:
getMessageCountin interfaceTopicMessageStore- Parameters:
clientId-subscriberName-- Returns:
- the outstanding message count
- Throws:
IOException
-
lookupSubscription
org.apache.activemq.command.SubscriptionInfo lookupSubscription(String clientId, String subscriptionName) throws IOException Finds the subscriber entry for the given consumer info- Specified by:
lookupSubscriptionin interfaceTopicMessageStore- Parameters:
clientId-subscriptionName-- Returns:
- the SubscriptionInfo
- Throws:
IOException
-
getAllSubscriptions
Lists all the durable subscriptions for a given destination.- Specified by:
getAllSubscriptionsin interfaceTopicMessageStore- Returns:
- an array SubscriptionInfos
- Throws:
IOException
-
addSubsciption
void addSubsciption(org.apache.activemq.command.SubscriptionInfo subscriptionInfo, boolean retroactive) throws IOException Inserts the subscriber info due to a subscription change If this is a new subscription and the retroactive is false, then the last message sent to the topic should be set as the last message acknowledged by they new subscription. Otherwise, if retroactive is true, then create the subscription without it having an acknowledged message so that on recovery, all message recorded for the topic get replayed.- Parameters:
subscriptionInfo-retroactive-- Throws:
IOException
-