Forum Discussion

678's avatar
678
Regular Contributor
6 years ago

ReadyAPI org.apache.xmlbeans.impl.values.XmlValueOutOfRangeException: Invalid boolean value

I am getting below error frequently - can any one help here      ERROR: org.apache.xmlbeans.impl.values.XmlValueOutOfRangeException: Invalid boolean value 'M' org.apache.xmlbeans.impl.values.Xml...
  • Nastya_Khovrina's avatar
    Nastya_Khovrina
    6 years ago

    OK, can you please share the solution once you find it with our Support team?

richie's avatar
richie
Community Hero
6 years ago
Hey 678,

Without knowing anything about your tests or code, i'd guess looking at the exception you have a boolean type attribute and it appears you're trying to pass it an invalid value of 'M'

Cheers,

richie
  • 678's avatar
    678
    Regular Contributor
    6 years ago

    i checked all my groovy scripts where i am not used any where as boolen value = M 

    • 678's avatar
      678
      Regular Contributor
      6 years ago

      not only invalid boolean value 'M' 

       

      i am getting few other same error like 

       

      ERROR: org.apache.xmlbeans.impl.values.XmlValueOutOfRangeException: Invalid boolean value 'c40b'

      ERROR: org.apache.xmlbeans.impl.values.XmlValueOutOfRangeException: Invalid boolean value 'rtio'

       

       

      • richie's avatar
        richie
        Community Hero
        6 years ago

        Hey 678 

         

        The exception response you're getting is pretty specific - you've definitely got some sort of problem where you have a boolean attribute somewhere and it doesn't like the values it's getting.

         

        Is the error occurring on specific tests? All tests? Specific Test Steps?  What is the test step that this is occurring on actually doing?  Is it a groovy step? or SOAP/REST request?

         

        Those values  'rtio',  'c40b', 'M' are pretty specific - so your test as it executes is reading off those values from somewhere.

         

        This should be straight forward to solve if you can provide a bit more info - and the fact that you have multiple instances on this leads me to believe you've got the same mistake in multiple tests.

         

        thanks man,

         

        richie