<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to bugs</title><link>https://sourceforge.net/p/nagiosappender/bugs/</link><description>Recent changes to bugs</description><atom:link href="https://sourceforge.net/p/nagiosappender/bugs/feed.rss" rel="self"/><language>en</language><lastBuildDate>Mon, 27 Jun 2011 09:12:06 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/nagiosappender/bugs/feed.rss" rel="self" type="application/rss+xml"/><item><title>Problem with encryption</title><link>https://sourceforge.net/p/nagiosappender/bugs/3/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Using simple XOR encryption, the server reports this error "Received invalid packet type/version from client - possibly due to client using wrong password or crypto algorithm?".&lt;/p&gt;
&lt;p&gt;This is due to the encryption_method variable in NagiosAppender class: i.e. if I use the configuration file to sets the encryption_method parameter, when the send_nsca(String, int) method have been invoked, it use the global encryption_method variable, but nobody's sets it. &lt;/p&gt;
&lt;p&gt;To resolve it,&lt;br /&gt;
- adds the getEncryption_method getter in Nsca class&lt;br /&gt;
- in setConfigFile(String) method, after nagiosClient.setConfigFile(value), adds encryption_method = nagiosClient.getEncryption_method()&lt;/p&gt;
&lt;p&gt;I attach a zip file with the java source modified surround by mbm099 comments&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Francesco Dalan</dc:creator><pubDate>Mon, 27 Jun 2011 09:12:06 -0000</pubDate><guid>https://sourceforge.netf6b1d019f5e82e448efd14f5a0ac964044a06053</guid></item><item><title>Socket timeout required</title><link>https://sourceforge.net/p/nagiosappender/bugs/2/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;There were some firewall / network issues resulting in our module hanging when trying to send messages to the Nagios server.  To prevent any future network issues from impacting our module, a socket timeout value added to the code and applied to the new socket.   .&lt;br /&gt;
&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Aaron Wodrich</dc:creator><pubDate>Tue, 17 Nov 2009 18:45:16 -0000</pubDate><guid>https://sourceforge.net40da7f245f0c8cfce0a28eefb224976f1595ea56</guid></item><item><title>Need to refactor failed connection attempts</title><link>https://sourceforge.net/p/nagiosappender/bugs/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Need to determine the most appropriate behavior for a&lt;br /&gt;
failed socket connection attempt ... instead of the&lt;br /&gt;
current model, which catches all exceptions.&lt;/p&gt;
&lt;p&gt;This is a classic error handler situation? Or worst&lt;br /&gt;
case a LogLog- like message. (great for new people&lt;br /&gt;
using the appender when they dumb  like me and have&lt;br /&gt;
something local preventing the connection).I'll have&lt;br /&gt;
more feedback once we've configured Nagios locally and&lt;br /&gt;
can  feed events to it.cheers,Paul Smith&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jar Lyons</dc:creator><pubDate>Mon, 01 Aug 2005 16:33:17 -0000</pubDate><guid>https://sourceforge.netce06ca033db99829601f6abf97dbc71b1d1c8a1d</guid></item></channel></rss>