IBM Support

IZ58882: BYTES READ PRIOR TO AN INTERRUPTEDIOEXCEPTION CAN BE OVERWRITTEN ON THE NEXT READ

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Problem between a JMS client and a queue manager, when using
    ISDN/DSL.
    During a MQGET the client gets:
    MQJMS2002: failed to get message from MQ queue
    Reason code RC 2009, MQRC_CONNECTION_BROKEN.
    .
    Conclusion:
    .
    When an InterruptedIOException is caught and handled, MQ assumes
    that a socket timeout has occurred and will initiate a retry
    and read the data again.
    In cases where part of the data has already been read
    the data received is ignored and will be overwritten.
    .
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of the WebSphere MQ Version 6.0.2
    classes for Java and classes for Java Message Service (JMS).
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows) +Java
    ****************************************************************
    PROBLEM SUMMARY:
    The readFully() method, used internally by the WebSphere MQ
    classes for Java and classes for JMS to read data from a
    socket, did not have the ability to record the number of bytes
    which had been transferred prior to an InterruptedIOException
    being thrown.
    
    The InterruptedIOException itself has a field called
    bytesTransferred but this does not work either due to a Java
    bug.
    

Problem conclusion

  • The readFully() call has been replaced with an iterative call to
    readByte() so that the number of bytes that have been read can
    be recorded, and any subsequent attempts to read bytes
    following a connection error can resume from the correct
    position.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v6.0
    Platform           Fix Pack 6.0.2.9
    --------           --------------------
    Windows            U200313
    AIX                U828012
    HP-UX (PA-RISC)    U827381
    HP-UX (Itanium)    U827383
    Solaris (SPARC)    U827693
    Solaris (x86-64)   U828055
    iSeries            tbc_p600_0_2_9
    Linux (x86)        U827380
    Linux (x86-64)     U827694
    Linux (zSeries)    U827590
    Linux (Power)      U827382
    Linux (s390x)      U827695
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available, information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ58882

  • Reported component name

    WMQ LIN X86 V6

  • Reported component ID

    5724H7204

  • Reported release

    600

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-08-18

  • Closed date

    2009-09-30

  • Last modified date

    2009-10-12

  • 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

    WMQ LIN X86 V6

  • Fixed component ID

    5724H7204

Applicable component levels

  • R600 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
31 March 2023