IV12829: Common console connector for OMNIbus creating javaxx.log files

IBM Tivoli Monitoring 6.2.2 Fix Pack 9 (6.2.2-TIV-ITM-FP0009)

APAR status

• Closed as program error.

Error description

• *************************** APAR Template ********************
  
  
  Please open an apar with the following severity and information:
  Severity:         3
  Approver:        sm
  Reported Release:622
  Compid:          5724C04PS Tivoli Enterprise Portal Server
  Abstract:        Unexpected java log created
  
  Environment:
  Customer had an issue with ITM622 FP6 on aix6.1
  
  Problem Description:
  The issue is that the common console connector for OMNIbus keeps
  creating javaxx.log and javaxx.log.lck files in the /home/root
  directory
  (the teps is running as root) and that's filling up the
  filesystem.
  
  Detailed Recreation Procedure:
  
  1) make sure TEPS configured with OMNIBUS Connector
  .
  2) While TEPS is running, STOP OMNIBUS server
  .
  After a while, EMPTY java files are created in roots home
  directory... all depends on the RECONNECT interval, if set
  to 20 seconds.. every 20 seconds these java files are
  created
  
  Related Files and Output:
  
  
  
  ************************ End of APAR Template ***************
  

Local fix

• no workaround is available.
  

Problem summary

• Stopping the common event console connector for OMNIbus while
  the portal server is running may rapidly consume the file system
  space.
  
  
  The common event console connector for OMNIbus creates files
  named javaxx.log and javaxx.log.lck in the home directory of the
  user when the portal server fails to connect to OMNIbus server.
  This consumes excessive file system space.
  

Problem conclusion

• The condition has been resolved so that the log files are not
  created repeatedly when a connection to OMNIbus server fails.
  
  The fix for this APAR is contained in the following maintenance
  packages:
    | fix pack | 6.2.2-TIV-ITM-FP0009
    | fix pack | 6.2.3-TIV-ITM-FP0002
  

Temporary fix

Comments

APAR Information

• 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

  TEPS

• Fixed component ID

  5724C04PS

Applicable component levels

• R622 PSY

     UP