IBM Support

IV30839: ORG.XML.SAX.SAXPARSEEXCEPTION: INVALID BYTE 3 OF 3-BYTE UTF-8 SEQUENCE WHILE RUNNING REPORTS WITH TCR

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When running a report using the WSRR reporting plugin in eclipse
    or TCR, reports
    fail with the following exception:
    
    org.eclipse.birt.data.engine.odaconsumer.PreparedStatement
    execute
    SEVERE: Cannot execute statement.
    org.eclipse.datatools.connectivity.oda.OdaException ;
    com.ibm.sr.reporting.exception.ConnectionException: The
    following
    error occurred whilst attempting to parse a response from a WSRR
    instance: org.xml.sax.SAXParseException: Invalid byte 3 of
    3-byte UTF-8 sequence
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of WebSphere Service Registry and Repository version 6.3.0
    and 7.0.0
    
    ****************************************************************
    PROBLEM SUMMARY:
    When you attempt to run a BIRT report either:
    
    a) Using an Eclipse environment that has the WSRR reporting
    plugin installed
    
    or
    
    b) From Tivoli Common Reporting (TCR) that is using the
    reporting runtime plugin JAR supplied within the WSRR
    reporting plugin archive site file
    
    the following exception occurs:
    
    org.xml.sax.SAXParseException: Invalid byte 3 of 3-byte UTF-8
    sequence
    

Problem conclusion

  • Input from the WSRR server is now correctly read as a UTF-8 byte
    sequence to ensure it is parsed correctly.
    
    This fix is targeted for inclusion in fix pack 5 for WSRR v6.3
    and fix pack 6 for WSRR v7.0.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV30839

  • Reported component name

    SERVICE REGISTR

  • Reported component ID

    5724N7200

  • Reported release

    630

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-25

  • Closed date

    2012-11-05

  • Last modified date

    2012-11-05

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    SERVICE REGISTR

  • Fixed component ID

    5724N7200

Applicable component levels

  • R630 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSWLGF","label":"WebSphere Service Registry and Repository"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.3","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
05 November 2012