IBM Support

IV72740: CREATING JAVA THREAD WITHIN PROCESS THREAD RENAMES THE PROCESS N AME TO 'MAIN' ON LINUX

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Error Message: No error. Process name is changed on Linux.
    .
    Stack Trace: N/A
    .
    

Local fix

Problem summary

  • Attempt to create a java thread within the process thread alters
    the name of the process and renames it to 'main'
    

Problem conclusion

  • Process name is reserved and name is not changed on Linux
    .
    This APAR will be fixed in the following Java Releases:
       7    SR9 FP 10 (7.0.9.10)
       7 R1 SR3 FP10  (7.1.3.10)
       6    SR16 FP7  (6.0.16.7)
       8    SR1 FP10  (8.0.1.10)
    .
    Contact your IBM Product's Service Team for these Service
    Refreshes and Fix Packs.
    For those running stand-alone, information about the available
    Service Refreshes and Fix Packs can be found at:
               https://www.ibm.com/developerworks/java/jdk/
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV72740

  • 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

    2015-04-24

  • Closed date

    2015-04-27

  • Last modified date

    2015-06-29

  • 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

  • R600 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