IBM Support

LO89745: TRAVELER GOES IN TO CONSTRAINED STATE WHEN LARGE NUMBER OF USERS ARE LOAD BALANCED TO SPECIFIC SERVER

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • In a IBM Traveler if a lot of users are load balance to one
    server this cause a constrained in Traveler because all of these
     users are trying to update the same entry in the Traveler
    database.  If the database ends up being a little slow at the
    time a lot of users are being load balanced to new server then
    the updates of UpdateTsGlobalHeartbeat is taking very long time.
      This is seen in the following IBM Traveler stats
       Database.Query.Histogram.UpdateTsGlobalHeartbeat.000-001 =
    2081
       Database.Query.Histogram.UpdateTsGlobalHeartbeat.001-002 = 38
       Database.Query.Histogram.UpdateTsGlobalHeartbeat.002-005 = 70
       Database.Query.Histogram.UpdateTsGlobalHeartbeat.005-010 = 55
       Database.Query.Histogram.UpdateTsGlobalHeartbeat.010-030 =
    182
       Database.Query.Histogram.UpdateTsGlobalHeartbeat.030-060 =
    400
       Database.Query.Histogram.UpdateTsGlobalHeartbeat.060-120 =
    562
       Database.Query.Histogram.UpdateTsGlobalHeartbeat.120-Inf =
    1281
    

Local fix

  • The customer needs to ensure they have run maintenance on the
    database and there are not any performance issue on the database
     server to reduce the probability of this issue happening.
    

Problem summary

  • To improve database performance the IBM Traveler server has
    begun limitting the number of concurrent transactions.  In this
    case the load ballancing of a large number of users caused a
    spike in transactions which then caused a constrained state with
    the new lower transaction limits.
    

Problem conclusion

  • The IBM Traveler server was updated to ensure the load balancing
    of users did not cause a transaction spike in this scenario.
    

Temporary fix

Comments

APAR Information

  • APAR number

    LO89745

  • Reported component name

    LOTUS NOTES TRA

  • Reported component ID

    5724E6204

  • Reported release

    901

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-07-26

  • Closed date

    2016-08-16

  • Last modified date

    2016-08-16

  • 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

    LOTUS NOTES TRA

  • Fixed component ID

    5724E6204

Applicable component levels

  • R901 PSY

       UP



Document information

More support for: IBM Traveler

Software version: 9.0.1

Reference #: LO89745

Modified date: 16 August 2016