Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-1317

org.jboss.test.jbossmx.compliance.monitor.BasicTestCase StringMonitor null attribute error notifications

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Blocker
    • JBossAS-3.2.7 Final
    • JBossAS-3.2.7 Final
    • JMX
    • None

    Description

      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>
      ---------------------------------

      Attachments

        Issue Links

          Activity

            People

              starksm64 Scott Stark (Inactive)
              starksm64 Scott Stark (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: