Opened 11 years ago

Last modified 10 years ago

#929 new defect

IZ693: sdmadm mc prints invalid error message when parsing a numerical XML attribute

Reported by: rhierlmeier Owned by:
Priority: normal Milestone:
Component: hedeby Version: 1.0u3
Severity: Keywords: Sun util


[Imported from gridengine issuezilla]

        Issue #:      693          Platform:     Sun         Reporter: rhierlmeier (rhierlmeier)
       Component:     hedeby          OS:        All
     Subcomponent:    util         Version:      1.0u3          CC:    None defined
        Status:       NEW          Priority:     P3
      Resolution:                 Issue type:    DEFECT
                               Target milestone: 1.0u5next
      Assigned to:    rhierlmeier (rhierlmeier)
      QA Contact:     rhierlmeier
       * Summary:     sdmadm mc prints invalid error message when parsing a numerical XML attribute
   Status whiteboard:

     Issue 693 blocks:
   Votes for issue 693:     Vote for this issue

   Opened: Thu Nov 12 00:45:00 -0700 2009 


   If you put a non numerical character into a numerical attribute of a XML
   configuration of SDM component you get an inproper error message.  In the
   following example the attribute urgency of a slo definition has an invalid value:

   % sdmadm mc -c sge
   <common:componentConfig ...>
           <common:slo xsi:type="common:FixedUsageSLOConfig" urgency="aa"
   Error: Not a number: aa

   The error message does not contain any hint what attribute has the wrong value.


   Invalid or improper error messages can confuse the user. At least a hint what
   attribute has the invalid value should be printed.


   The problem is caused by a JAXB bug. See

   This bug has been fixed with JAXB 2.1.12. We should upgrade soon.


   There is not workaround possible.

   How to test

   Extend XMLUtilTest. Write a new test method that creates an xml file with and
   numerical attribute. But non numerical characters into the attribute. Load the
   file with XMLUtil.loadAndValidate. Check the error message it should contain a
   hint what attribute is affected.

   ETC: 1PD
               ------- Additional comments from rhierlmeier Wed Nov 25 07:21:12 -0700 2009 -------
   Milestone changed

Change History (0)

Note: See TracTickets for help on using tickets.