It's worth noting that if you happen to be using durable subscriptions (the
durable parameter is set to true in the JmsMessagingClient constructor) and
your client goes away, the broker will store messages until your client
re-establishes a connection. When your client reconnects, all of those
stor
If your client is only receiving messages, then the Fedora JMS service will not
be disturbed by it disappearing, although calling .stop may allow it to release
some resources, depending on how you've configured your repository's Messaging
module and ActiveMQ substrate.
---
A. Soroka
Online Libr
Hello, Conal --
You may find this page of use, especially the section "Configuring
Messaging with ActiveMQ for Higher Availability".
https://wiki.duraspace.org/display/FCR30/Messaging
-- Scott
On 05/23/2011 02:21 AM, Conal Tuohy wrote:
> I know very little about JMS but I have written a JMS Me
I know very little about JMS but I have written a JMS Messaging client
to listen for changes to Fedora objects, using an instance of
org.fcrepo.client.messaging.MessagingClient.
My application is a stand-alone application which does nothing but
listen for changes and propagate data elsewhere. I
