IC84991: LOGS UNDER ESSNITRACE\ HAVE MANY ZIP FILES CAUSING HUGE LOG PKG

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as fixed if next.

Error description

  • Logger.jar is using the parameter -DswapTrimming which is
    creating lots of zipped files under the essniClient log
    directory that have the appearance of:
    niClient.log.bk.zip.YYYY-MM-DD_HH-MM-SS
    niTransmission.log.bk.zip.YYYY-MM-DD_HH-MM-SS
    

Local fix

  • Manually remove these files before taking a TPC-R diagnostic
    package.
    
    1. open the
    ${WAS_HOME}/profiles/default/properties/niClientLogging.properti
    es
    2. Edit the file and comment out the following properties
    ClientHandler.level
    CAHandler.level
    TransmissionHandler.level
    com.ibm.storage.ess.ni.level
    com.ibm.storage.ess.ni.ca.level
    com.ibm.storage.ess.ni.communication.extensions.NITransmissionLo
    gger.level
    
    3. Replace the above property settings with
    ClientHandler.level = ERROR
    CAHandler.level = ERROR
    TransmissionHandler.level = ERROR
    com.ibm.storage.ess.ni.level = ERROR, THROWABLE
    com.ibm.storage.ess.ni.ca.level = ERROR
    com.ibm.storage.ess.ni.communication.extensions.NITransmissionLo
    gger.level = ERROR, THROWABLE
    
    4. Restart the TPC for Replication WebSphere instance to pick up
    the changes
    
    Now only error entries will be seen in the logs.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * all                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Customers upgrading to 4.2.2.2 will now see extemporaneous   *
    * logging in the logs/CSM/essniTrace directory. The logs will  *
    * take up a large amount of disk space.                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply the workaround provided in the "Temporary         *
    * Fix" section.                                           *
    ****************************************************************
    A generic JVM argument was set that caused this additional
    logging to occur.
    

Problem conclusion

  • The generic JVM argument will be set to false
    

Temporary fix

  • A workaround is to create a jacl script e.g.
    setGenJvmArg.jacl<br/>and enter:<br/>set genericJvmArg
    {{genericJvmArguments
    &quot;-DSwapTrimming=false&quot;}}<br/><br/>Then run the .jacl
    script -- see the following info center for instructions on how
    to run jacl scripts for
    WebSphere:<br/>http://pic.dhe.ibm.com/infocenter/wasinfo/v6r1/to
    pic/com.ibm.websphere.wsfep.multiplatform.doc/info/ae/ae/txml_la
    unchscript.html
    

Comments

APAR Information

  • APAR number

    IC84991

  • Reported component name

    TPC

  • Reported component ID

    5608TPC00

  • Reported release

    510

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-06-29

  • Closed date

    2012-08-03

  • Last modified date

    2012-11-02

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • R510 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Storage Productivity Center

Software version:

510

Reference #:

IC84991

Modified date:

2012-11-02

Translate my page

Machine Translation

Content navigation