IBM Support

PK76400: PROBLEMS USING ANT TO DEPLOY APPLICATIONS WITH 64 BIT CODE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The exception seen when ANT starts the server is:
    
    [10/15/08 13:52:05:824 EDT] 0000000a AdminTool     E
    ADMU0111E:
    Program exiting with error: java.lang.UnsatisfiedLinkError:
    /opt/IBM/WebSphere/AppServer/bin/libWs60ProcessManagement.so:
    ld.so.1:
    java: fatal:
    /opt/IBM/WebSphere/AppServer/bin/libWs60ProcessManagement.so:
    wrong ELF
    class: ELFCLASS64 (Possible cause: architecture word width
    mismatch)
    
    This is usually due to a 32-bit to 64-bit mismatch of library
    files.
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of WebSphere Application Server   *
    *                  V6.1 ws_ant tasks on a 64-bit platform.     *
    ****************************************************************
    * PROBLEM DESCRIPTION: The ws_ant task launcher may fail to    *
    *                      execute the WebSphere Application       *
    *                      Server Ant tasks on a 64-bit platform.  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    On a 64-bit platform the following error may occur when
    executing any WebSphere Application Server Ant task:
    
    Program exiting with error: java.lang.UnsatisfiedLinkError:
    /opt/IBM/WebSphere/AppServer/bin/libWs60ProcessManagement.so:
    ld.so.1:
    java: fatal:
    /opt/IBM/WebSphere/AppServer/bin/libWs60ProcessManagement.so:
    wrong ELF class: ELFCLASS64 (Possible cause: architecture
    word width mismatch)
    
    This error is happening because the -d64 JVM propery is being
    added for any Ant task invocation on a 64-bit platform.
    

Problem conclusion

  • The fix for this problem is to ensure that this JVM
    property is only defined when run on 64-bit Solaris and HP-UX
    platforms as the -d64 property is only supported on these
    platforms.
    
    The fix for this APAR is currently targeted for inclusion in
    fixpack 6.1.0.23.  Please refer to the Recommended Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK76400

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    61S

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-11-25

  • Closed date

    2008-12-05

  • Last modified date

    2008-12-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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R61A PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61W PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021