Jmx4Perl 0.72 has been released which is a pure bug-fix release.
Thruk 0.70 has been released at (download). The three major changes from user perspective are
Since version 0.70,
check_jmx4perl has support for configuration files. JMX Nagios checks are now considerably simpler to configure and multi checks add even more performance and flexibility.
This post explains why a dedicated Tomcat Connector reserved for the jmx4perl agent is a useful thing.
TestNG groups add great flexibility to the Citrus test execution. We are able to divide all tests into several groups reaching a sophisticated seperation of concerns in our test setup. As an example I want to classify some of my functional Citrus tests as “long-running”. These tests may not apply to continuous execution every time I package my project. Instead of this I want to set up a scheduled integration build to execute those long-running tests in a time schedule.
Citrus 1.1 release is here (download)! The release comes with a bunch of new features and bugfixes. Here is a short list of major features and changes in this release:
Die Plugins check_oracle_health und check_mssql_health haben mit den Versionen 1.6.6 bzw. 1.5.6 ein neues Feature bekommen. Critical- und Warning-Schwellwerte können jetzt auch direkt in der Datenbank hinterlegt werden. Bei Änderungswünschen muss der DBA nun nicht mehr den Nagios-Administrator belästigen, damit dieser die entsprechenden Servicedefinitionen anpasst.
If you have defined services using the nrpe mechanism, you might know the following scenario:
The NRPE daemon fails and all services using it go critical. One first step to avoid these false alarms is to create an additional service which monitors the NRPE daemon itself (called check_nrpe_daemon in this example) and install a dependency between your services and check_nrpe_daemon.
I’m happy to announce the new jmx4perl release 0.70 with a lot of new features. The most exciting new stuff are configuration files and multi-checks for
check_jmx4perl, a new Java client library and the start of a readline based JMX shell
j4psh with syntax highlighting and command line completion.
By setting the SOAP mustUnderstand header attribute to “1”, you indicate that the service provider must process the SOAP header entry. In case the service provider is not able to handle this special header a SOAP fault server error is sent back to the calling client. In this post I would like to point out an easy way to support these mustUnderstand headers when simulating SOAP WebServices with Citrus.