IC86820: (CM) AFTER INSTALL OF 64BIT VERSION OF SSPCM, THE SSPCM STARTUP SCRIPT DEFAULTS TO THE 32 BIT JAVA ON SOLARIS

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • Customer updated SSPcm to run using the 64 bit version but the
    default remain with using the 32 bit Java version.
    
    Workaround: Change the SSPcm startup script to point to the 64
    bit Java version that we ship with the product.
    

Local fix

  • Document: Workaround Setup for SSPcm and SSPeng to use IBM
    64bit Java on Solaris
    
    Purpose: To allow SSPcm and SSPeng to use 64bit java when using
    Solaris.  By default, the startup scripts are pointing to the
    32 bit java program in the
    current install directory of the product.  During the original
    installation, the 64bit java is also installed on Solaris.
    
    Task:
    After updgrading, the user will need to point the startup
    scripts to the 64bit java.
    
    1) First verify that the 64bit java exist in the product
    installed path by listing the file:
    
    ls -l <SSPcmInstallDir>/jre/bin/sparv9/java
    ls -l <SSPengInstallDir>/jre/bin/sparv9/java
    
    2) If file exist, change the startup scripts by doing the
    following:
    
    SSPcm Startup Script (startCM.sh):
    
    In <SSPcmInstallDir>\bin\startCM.sh you will see the following
    3 lines that is currently pointing to the 32bit java on Solaris:
    
    Example:
    Old:
    PP=`"/home/SSPcm/jre/bin/java" -cp
    ${LIB_DIR}/sterling/componentCommon.jar...
    echo "${PP}" | nohup "/home/SSP/ssp3410_cm/jre/bin/java"
    -server -Xmx${MAXHEAP} -cp...
    nohup "/home/SSPcm/jre/bin/java" -server -Xmx${MAXHEAP} -cp
    ${CLASSPATH}...
    
    New Change:
    PP=`"/home/SSPcm/jre/bin/sparcv9/java" -cp
    ${LIB_DIR}/sterling/componentCommon.jar...
    echo "${PP}" | nohup "/home/SSPcm/jre/bin/sparcv9/java" -server
    -Xmx${MAXHEAP} -cp...
    nohup "/home/SSPcm/jre/bin/sparcv9/java" -server -Xmx${MAXHEAP}
    -cp ${CLASSPATH}...
    
    
    SSP Engine Startup Script (startEngine.sh):
    
    In the script <SSPengInstallDir>/bin/startEngine.sh you will
    see the following 3 lines that is currently pointing to the
    32bit java on Solaris:
    
    <SSPengInstallDir>/jre/bin/java
    
    Change the lines to reflect the path to the path to the 64bit
    Java.
    
    <SSPengInstallDir?/jre/bin/sparcv9/java
    
    Example:
    Old:
    PP=`"/home/SSPeng/jre/bin/java" -cp
    ${LIB_DIR}/sterling/componentCommon.jar
    com.sterlingcommerce.component.c...
    echo $PP | nohup "/home/SSPeng/jre/bin/java" -server
    -Xmx${MAXHEAP} -cp ${CLASSPATH} ${F} ${B} ${C}...
     nohup "/home/SSPeng/jre/bin/java" -server -Xmx${MAXHEAP} -cp
    ${CLASSPATH} ${F} ${B} ${C} -DvendorFile...
    
    New Change:
    PP=`"/home/SSPeng/jre/bin/sparcv9/java" -cp
    ${LIB_DIR}/sterling/componentCommon.jar
    com.sterlingcommerce.component.c...
    echo $PP | nohup "/home/SSPeng/jre/bin/sparcv9/java" -server
    -Xmx${MAXHEAP} -cp ${CLASSPATH} ${F} ${B} ${C}...
    nohup "/home/SSPeng/jre/bin/sparcv9/java" -server
    -Xmx${MAXHEAP} -cp ${CLASSPATH} ${F} ${B} ${C} -DvendorFile...
    
    Best Regards,
    
    Ricki L. Johnson
    

Problem summary

  • SSP on Solaris points to the 32-bit JRE, even though the 64-bit
    JRE is shipped.
    The Customer upgraded to SSP 3.3.01 on Solaris to get the 64-bit
    capability, but found that the JRE was only 32-bit. All the
    scripts to run the product and utilities point to the
    ./jre/bin/java executable, which is the 32-bit version of the
    JRE.  The 64-bit version of the jre is at
    ./jre/bin/sparcv9/java.
    

Problem conclusion

  • Updated the InstallAnywhere logic for the Solaris platform to
    properly build the scripts to point to the 64-bit version of the
    JRE at ./jre/bin/sparcv9/java.
    

Temporary fix

  • Manually update the SSP/bin/startEngine.sh and
    SSPcm/bin/startCM.sh scripts to point to the new java location
    at ./jre/bin/sparcv9/java. However, these scripts get rebuilt
    during any maintenance upgrade.
    

Comments

APAR Information

  • APAR number

    IC86820

  • Reported component name

    STR SECURE PROX

  • Reported component ID

    5725D0300

  • Reported release

    320

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-09-25

  • Closed date

    2012-10-30

  • Last modified date

    2012-10-30

  • 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

    STR SECURE PROX

  • Fixed component ID

    5725D0300

Applicable component levels

  • R331 PSY

       UP

  • R340 PSY

       UP

  • R341 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

Sterling Secure Proxy

Software version:

3.2

Reference #:

IC86820

Modified date:

2012-10-30

Translate my page

Machine Translation

Content navigation