I've been doing some playing around with Fedora and messaging, and investigating the problem in this issue:
https://jira.duraspace.org/browse/FCREPO-802 and after tinkering about with ActiveMQ, I uncovered a method to implement store-and-forward message delivery in Fedora. Basically this technique accomplishes the following: Fedora will: a) upon startup, load an ActiveMQ embedded broker b) configure the embedded broker to: i. forward Fedora messages to a remote broker, if the remote broker is available; ii. if the remote broker is not available, it will store the messages until the remote broker becomes available, at which point it will forward the messages to it c) use the ActiveMQ “failover” transport to attempt periodic reconnections to the remote broker when it is unavailable You can find instructions for setting this up at: http://sdg.library.wisc.edu/blog/2010/09/27/configuring-activemq-with-failover-in-fedora-for-higher-availability/ -- Scott -- Scott Prater Library, Instructional, and Research Applications (LIRA) Division of Information Technology (DoIT) University of Wisconsin - Madison pra...@wisc.edu ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Fedora-commons-users mailing list Fedora-commons-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
