IY68304: ERROR MESSAGE IN CLIENT MSG.LOG FILE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Error message that appears in some Manger Client msg.log files.
    
    KEGCAH020 Error While Processing Collector Info -
    java.lang.NullPointerException
    KEGCCL020 Stack Trace for Exception:
    java.lang.NullPointerException
    java.lang.NullPointerException
          at KEGC_Client.setSettingChange(KEGC_Client.java:3258)
          at
    KEGC_AcceptRequestHelper.ProcessCollectorInfo(KEGC_AcceptRequest
    Helper.java:1156)
          at KEGC_AcceptRequestHelper.run(Compiled Code)
    
    Error when Manager Client communicates to Central Control.
    The problem is related to synchronization.  When KEGC_Client is
    initializing, it creates objects in its path, and some of these
    objects are being used as a thread.  In the case of our problem,
    KEGC_AcceptHelper object which receives the requests from
    collectors is created at the start of KEGC_Client, and then the
    thread is started.  Depending on how the operating system
    dispatcher is behaving, it might dispatch the object or not.  If
    the object is dispatched (Which means the KEGC_Client object is
    now pre-empted, so it is not running), it calls method
    "setSettingChange" in KEGC_Client which calls one of the method
    calls in the KEGC_HeartBeat.  But, KEGC_HeartBeat object has not
    been created yet, so it will result in a null pointer exception.
    
    But, if KEGC_AcceptHelper is not dispatched at the time of
    KEGC_Client initialization, then the initialization will
    continue, and it will create KEGC_HeartBeat object, and now when
    KEGC_AcceptHelper thread is started, we are not going to get the
    null pointer exception, because the KEGC_HeartBeat object has
    been created.  That is why sometimes you see the error, and
    sometimes you don't.
    
    Cause:
    When the ETE Collector starts up it communicates configuration
    info to the Manager Client. The Manager Client may not have
    completed its initialization when this communication arrives.
    Subsequent reference to an initialized state object causes
    NullPointerException.
    
    Effect:
    Central Control will show incorrect state of the ETE Collector.
    No other effect.
    

Local fix

  • Startup Manager Client before the ETE Collector.
    

Problem summary

  • Error when Manager Client communicates to Central Control.
    

Problem conclusion

  • Fix available
    

Temporary fix

Comments

APAR Information

  • APAR number

    IY68304

  • Reported component name

    ETEWTH ENTRPS S

  • Reported component ID

    5724K4100

  • Reported release

    202

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2005-02-22

  • Closed date

    2005-05-20

  • Last modified date

    2005-05-20

  • 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

    ETEWTH ENTRPS S

  • Fixed component ID

    5724K4100

Applicable component levels

  • R202 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli ETEWatch Starter Kit - Professional Edition

Software version:

202

Reference #:

IY68304

Modified date:

2005-05-20

Translate my page

Machine Translation

Content navigation