There are 3 errors in the StringMonitor tests due to the expectation of an jmx.monitor.error.attribute notification resulting from the monitored attribute being null. The java5 implementation explicitly ignores this condition and its certainly not clear from the spec that such an error should be generated for this condition.

Suite: org.jboss.test.jbossmx.compliance.monitor.BasicTestCase
Test: testStringBothNotification
Type: failure
Exception: junit.framework.AssertionFailedError
Message: expected:<1> but was:<0>
---------------------------------

Suite: org.jboss.test.jbossmx.compliance.monitor.BasicTestCase
Test: testStringMatchNotification
Type: failure
Exception: junit.framework.AssertionFailedError
Message: expected:<1> but was:<0>
---------------------------------

Suite: org.jboss.test.jbossmx.compliance.monitor.BasicTestCase
Test: testStringDifferNotification
Type: failure
Exception: junit.framework.AssertionFailedError
Message: expected:<1> but was:<0>
---------------------------------