<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Stomp on cd ~</title><link>https://www.rottenbytes.info/tags/stomp/</link><description>Recent content in Stomp on cd ~</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 27 Sep 2010 21:30:19 +0000</lastBuildDate><atom:link href="https://www.rottenbytes.info/tags/stomp/index.xml" rel="self" type="application/rss+xml"/><item><title>STOMP-ed nagios</title><link>https://www.rottenbytes.info/2010/09/27/stomp-ed-nagios/</link><pubDate>Mon, 27 Sep 2010 21:30:19 +0000</pubDate><guid>https://www.rottenbytes.info/2010/09/27/stomp-ed-nagios/</guid><description>&lt;p&gt;&lt;img class="alignleft size-full wp-image-62" title="eth0" src="http://www.rottenbytes.info/wp-content/uploads/2009/02/eth0.jpg" alt="eth0" width="80" height="103" /&gt;Basing more and more stuff on mcollective means relying more and more on one of its underlying components : the activeMQ middleware, and more precisely the stomp connector. I hit a weird bug a few days ago and realized that I was not &lt;em&gt;functionnaly&lt;/em&gt; monitoring this part of the system. The port was bound and responded to connections, subscriptions were possible but messages didn’t pass through.So I wrote this little &lt;a href="http://github.com/rottenbytes/Scripts/blob/master/monitoring/check_stomp.rb"&gt;plugin&lt;/a&gt; that makes this possible : it creates a random string, sends it to a queue and then reads the queue to check if the result is the same.&lt;/p&gt;</description></item></channel></rss>