LO70481: ONLINE USERS ARE SEEN AS OFFLINE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as fixed if next.

Error description

  • There was one occurrence of this problem, when some of the
    online users were
    seen as offline. The problem was on a single server, users on
    the same server
    saw these other users as offline. The problem seen in the
    available traces is
    as follows:
    User Morgan User1 logged in at 10:02 EST on server A
    and stayed logged
    in since then. Online directory process on server A sent a
    locate response to
    SM on server A about this login. However for some reason I see
    that SM still
    considers this user not located at a later time. Unfortunately
    the provided
    buddy list traces don't cover 10:02. I have buddy list traces
    only since 11:15.
    Without these traces I have no way
    to know what went wrong. I reviewed the relevant parts of the
    buddy list and
    online directory code, but couldn't find the problem. I assume
    that the other
    users in the list are not seen as online because of the same
    problem as with User1.
    
    The relevant SM traces:
    Line 6294: [ 11:35:14.752 | 27.06.2012 | INFO | b ] :
    WatchedObject :
    addWatcher : watcher [CN=xxxxn
    xxxxxg,OU=CA10,OU=10,O=] is added.
    Message Type=104; Watcher Id={CN=xxxxxx
    xxxxx,OU=CA10,OU=10,O=xxxxx,};
    Watcher Login Id={e21f9aa9 09c771e99,}; Watched Object
    Id={CN=xxxxx
    xxxxxxxx,OU=CA10,OU=10,O=xxxxxx,};
     Line 6295: [ 11:35:14.752 | 27.06.2012 | INFO | b ] :
    WatchedObject :
    addWatcher : watcher [CN=xxxxx
    xxxxxxxx,OU=CA10,OU=10,O=xxxxx] already
    watches CN=xxxxx xxxxxxxx,OU=CA10,OU=10,O=xxxxxx, and so
    was not added.
    Message Type=104; Watcher Id={CN=xxxxxx
    xxxxxxxx,OU=CA10,OU=10,O=xxxxx,};
    Watcher Login Id={e21f9aa9 09c771e99,}; Watched Object
    Id={CN=xxxxxxx
    Xxxxxxxxx,OU=CA10,OU=10,O=xxxxxx,};
     Line 6295: [ 11:35:14.752 | 27.06.2012 | INFO | b ] :
    WatchedObject :
    addWatcher : watcher [CN=xxxxxx
    xxxxxxx,OU=CA10,OU=10,O=xxxxxx] already
    watches CN=xxxxxx xxxxxxxxx,OU=CA10,OU=10,O=xxxxxxx, and so
    was not added.
    Message Type=104; Watcher Id={CN=xxxxxxx
    xxxxxxx,OU=CA10,OU=10,O=xxxxxx,};
    Watcher Login Id={e21f9aa9 09c771e99,}; Watched Object
    Id={CN=Morgan
    xxxxxxxxxxx,OU=CA10,OU=10,O=xxxxxx,};
     Line 6296: [ 11:35:14.752 | 27.06.2012 | INFO | b ] : User :
    handleSubscription : user [CN=xxxxxx
    xxxxxxxxxxxx,OU=CA10,OU=10,O=xxxxxxx
    location is in progress.  Message Type=104; Watcher
    
    
    
    
    
    
    
    The relevant online directory traces:
    Line 20421: 120627_100215.150,INF,OD_COMMU,User [CN=xxxxxx
    xxxxxxx  0,OU=10,O=xxxxx] up on server with loginId
    [0 09c771e99]
    Line 20422: 120627_100215.150,INF,OD_COMMU,response is sent for
    user [CN=xxxxxx
    xxxxxxx,OU=CA10,OU=10,O=USCOURTS] to loginId [e21ddf9b
    09c771e99] with
    server id [0 09c771e99]
    Line 20423: 120627_100215.150,INF,OD_COMMU,delete pending user
    [CN=xxxxxx
    xxxxxxxxxxx,OU=CA10,OU=10,O=USCOURTS]
    Line 20424: 120627_100215.150,INF,OD_COMMU,user [CN=xxxxxxx
    xxxxxxxxxxxxx,OU=CA10,OU=10,O=xxxxxxx] was added as online
    
    
    A buddy list hotfix version will be provided to the customer, in
    this version a
    particular print will be moved from info level to finest since
    this print is
    logged too much, and the majority of the content of the SM trace
    files is
    solely this print. The print was moved from finest to info level
    in a recent
    hotfix and it is located in WatchedObject::removeWatcher:
    s_logger.info("removeWatcher", "watched object [" +
    getId().getId() + "] is
    watched by watcher [" + sub.getWatcher().getId().getId()
    +"].");
    
    Moving it back to finest will allow covering greater time frame
    in SM traces.
    In addition there is a concern that with this print in info
    level, SM might not
    be able to run with info level enabled in some scenarios.
    

Local fix

  • NA
    

Problem summary

  • This APAR was closed as FIN. We have deferred the fix to a
     future release.
    

Problem conclusion

Temporary fix

Comments

  • This APAR is associated with SPR# LKON8VU98T.
    This APAR was closed as FIN. We have deferred the fix to a
     future release.
    

APAR Information

  • APAR number

    LO70481

  • Reported component name

    LOTUS SAMETIME

  • Reported component ID

    5724J2300

  • Reported release

    852

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-07-11

  • Closed date

    2012-12-05

  • Last modified date

    2012-12-05

  • 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

  • R852 PSN

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

IBM Sametime

Software version:

8.5.2

Reference #:

LO70481

Modified date:

2012-12-05

Translate my page

Machine Translation

Content navigation