IBM Support

IV65163: STRINGBUFFER WAS NOT THREAD-SAFE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Error Message: StringBuffer is not thread-safe.
    .
    Stack Trace:
    .
    

Local fix

Problem summary

  • StringBuffer was not implemented as thread-safe.
    

Problem conclusion

  • java.lang.StringBuffer.capacity and
    java.lang.StringBuffer.length are now thread-safe.
    .
    This APAR will be fixed in the following Java Releases:
       6 R1 SR8 FP2   (6.1.8.2)
       7    SR8       (7.0.8.0)
       7 R1 SR2       (7.1.2.0)
    .
    Contact your IBM Product's Service Team for these Service
    Refreshes and Fix Packs.
    For those running stand-alone, Java maintenance is available
    from:
               https://www.ibm.com/developerworks/java/jdk/
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV65163

  • Reported component name

    J9 COMMON CODE

  • Reported component ID

    620700127

  • Reported release

    260

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-09-23

  • Closed date

    2014-09-23

  • Last modified date

    2014-10-28

  • 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

    J9 COMMON CODE

  • Fixed component ID

    620700127

Applicable component levels

  • R260 PSY

       UP

  • R270 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
22 February 2022