Carl Nygard wrote:
> I wish it were that simple. We're using notifications to send a
> message over ActiveMQ message topic to an app server which is
> maintaining state for selective events for a customer-facing
> simplified GUI. If the app server goes down, it misses notification
> messages.
>
> If a notification method fails (i.e. ActiveMQ is down) will the
> notification be queued up and retried? If so, I can just make the
> ActiveMQ channel a durable queue and my problem is largely solved.
> I've already written the ActiveMQ notification plugin for OpenNMS, so
> that part's done.
I'd probably have used an xmmp client for the client side instead, but
isn't the point of ActiveMQ to hold messages until a client reads them?
Is your ActiveMQ server going down or just the application client?
--
Les Mikesell
lesmikes...@gmail.com
------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ
opennms-devel mailing list
To *unsubscribe* or change your subscription options, see the bottom of this
page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel
