IBM Support

IV54577: EVENT SYNC SUF REREADS CACHE FILE ON STARTUP

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The cache file that is being used by the situation update
    forwarder (SUF) is not being cleared after being read.
    When the SUF is restarted, it reprocesses all of the old events
    and generates out-of-sync errors.
    
    This message can be seen in the SUF
    
    Checkpoint.Checkpoint IBM
    Tivoli Monitoring  Tivoli Event Synchronization
    xxxxxxxxx IP Invalid cacheFileName,
    /opt/IBM/SitForwarder/persistence/situpdate_cache.log1, in
    lastread file. Using defaults.
    
    The code was expecting the short filename instead of the
    absolute path in the lastread.
    
    found in the synch_msg.log:
    
    <Message Id="KFAIT0018I" Severity="ERROR">
     <Time Millis="1389643230346"> 2014.01.13
    15:00:30.346-05:00</Time>
     <Server Format="IP">xxxxxxxxxxxxx</Server>
     <ProductId>Monitoring</ProductId>
     <Component>Tivoli Event Synchronization</Component>
     <ProductInstance></ProductInstance>
     <LogText><![CDATA[KFAIT0018I The (null) error occurred while
    processing a cache file.]]></LogText>
     <Source
    FileName="com.tivoli.candlenet.SituationUpdateForwarder"
    Method="pollCacheFile"/>
     <TranslationInfo Type="JAVA"
    Catalog="com.tivoli.candlenet.messages.TecSynchronizationMessage
    s"
    MsgKey="KFAIT0018"><Param><![CDATA[]]></Param></TranslationInfo>
     <Principal></Principal>
    </Message>
    

Local fix

  • Recreate:
    1. Install and configure event sync for OMNIbus.
    2. Acknowledge or close some events from ITM in the OMNIbus
    event list.
    3. Verify the event updates are successfully sent back to ITM.
    4. Stop and restart the SUF, and a log message for "Invalid
    cacheFileName" is seen in the log, though the file name is valid
    in the
    lastread file. That causes the SUF to reread and resend the
    events in
    the file.
    
    
    Workaround:
    Level 3 provided a new situpdate.jar file.
    Replace the current file which is in the jars subdir of the
    event sync install path.
    

Problem summary

  • The Situation Update Forwarder (SUF) rereads the event
    synchronization cache file from the beginning when it is
    restarted.
    
    
    When the Situation Update Forwarder (SUF) restarts, it locates
    its marker for the last event read using the lastread file in
    the cache file directory.  The SUF is checking for the wrong
    value for cache file name in the lastread file, so it assumes
    the file didn't exist and starts from the beginning.
    

Problem conclusion

  • Fixed the Situation Update Forwarder (SUF) check for cache file
    name, so the correct file name is used, and the SUF finds its
    marker for the last cache entry read.
    
    The fix for this APAR is contained in the following maintenance
    packages:
    
      | fix pack | 6.3.0-TIV-ITM-FP0003
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV54577

  • Reported component name

    TEMS

  • Reported component ID

    5724C04MS

  • Reported release

    623

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-01-27

  • Closed date

    2014-03-28

  • Last modified date

    2014-08-08

  • 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

    TEMS

  • Fixed component ID

    5724C04MS

Applicable component levels

  • R630 PSY

       UP



Document information

More support for: IBM Tivoli Monitoring V6
ITM Tivoli Enterprise Mgmt Server V6

Software version: 623

Reference #: IV54577

Modified date: 08 August 2014