IZ74588: CONNECTION MANAGER CRASHES DUE TO INCORRECT CLEANUP PROCESSING AFTER FAILED HTTP-TCP MOBILE NETWORK CONNECTION ATTEMPTS.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Lotus Mobile Connect 6.1.3 on RH Linux
    
    The external symptom for this report is that the Connection
    Manager core dumps (crashes, abnormally terminates) and then
    restarts itself.  In a wg.log of the problem the following
    messages are seen:
    
    http-tcp-lan0: maximum active session count (1026) exceeded,
    refusing connection [202.81.18.239:48947]
     21951:1235880864 (Apr 12 2010/15:46:29.8447):http-tcp-lan0:
    maximum active session count (1026) exceeded, refusing
    connection [202.81.18.239:48948]
     21951:-1769534560 (Apr 12 2010/15:46:30.6220):http-tcp-lan0:
    maximum active session count (1026) exceeded, refusing
    connection [202.81.18.239:48949]
     21951:1237982112 (Apr 12 2010/15:46:32.1071):http-tcp-lan0:
    maximum active session count (1026) exceeded, refusing
    connection [202.81.18.239:48950]
     21951:1235880864 (Apr 12 2010/15:46:32.6081):http-tcp-lan0:
    maximum active session count (1026) exceeded, refusing
    connection [202.81.18.239:48951]
     21951:-1769534560 (Apr 12 2010/15:46:34.3848):http-tcp-lan0:
    maximum active session count (1026) exceeded, refusing
    connection [202.81.18.239:48952]
    
    It would appear that the Connection Manager is not correctly
    cleaning up after a failed connection attempt to the HTTP-TCP
    based Mobile Network Connections (MNC's).  It leads to an out of
    memory condition eventually and the crash.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: LMC Connection Manager configured in a       *
    *                 cluster with HTTP Access Services            *
    *                 definitions.                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: CONNECTION MANAGER CRASHES DUE TO       *
    *                      INCORRECT CLEANUP PROCESSING  AFTER     *
    *                      FAILED HTTP-TCP MOBILE NETWORK          *
    *                      CONNECTION ATTEMPTS.                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The external symptom for this report is that the Connection
    Manager core dumps (crashes, abnormally terminates) and then
    restarts itself.  In a wg.log of the problem the following
    messages are seen:
    
    http-tcp-lan0: maximum active session count (1026) exceeded,
    refusing connection [202.81.18.239:48947]
    21951:1235880864 (Apr 12 2010/15:46:29.8447):http-tcp-lan0:
    maximum active session count (1026) exceeded, refusing
    connection [202.81.18.239:48948]
    21951:-1769534560 (Apr 12 2010/15:46:30.6220):http-tcp-lan0:
    maximum active session count (1026) exceeded, refusing
    connection [202.81.18.239:48949]
    21951:1237982112 (Apr 12 2010/15:46:32.1071):http-tcp-lan0:
    maximum active session count (1026) exceeded, refusing
    connection [202.81.18.239:48950]
    21951:1235880864 (Apr 12 2010/15:46:32.6081):http-tcp-lan0:
    maximum active session count (1026) exceeded, refusing
    connection [202.81.18.239:48951]
    21951:-1769534560 (Apr 12 2010/15:46:34.3848):http-tcp-lan0:
    maximum active session count (1026) exceeded, refusing
    connection [202.81.18.239:48952]
    
    It would appear that the Connection Manager is not correctly
    cleaning up after a failed connection attempt to the HTTP-TCP
    based Mobile Network Connections (MNC's).  It leads to an out of
    memory condition eventually and the crash.
    

Problem conclusion

  • A formal fix for this problem will be included in all product
    releases AFTER 6.1.4.  Until that time a temporary fix may be
    obtained from the IBM Lotus Mobile Connect Support Center.
    To obtain this APAR fix or technical support for Lotus Mobile
    Connect you may either visit the Lotus Mobile Connect On-line
    Support Center at http://www-947.ibm.com/support/entry/portal
    /Overview/Software/Lotus/Lotus_Mobile_Connect
    ('Open Service Request').  If you need to reach IBM Support
    in the U.S. call 1-800-IBM-SERV. For Support outside of the
    U.S. please visit the IBM Contacts page at http://www.ibm.com
    /planetwide/ to find the direct dial support number for your
    location.
    

Temporary fix

  • A temporary fix is now available for this APAR from the IBM
    Lotus Mobile Connect (LMC) Level 2 support center.  To obtain
    this fix please open a Problem Management Record (PMR) either by
    submitting a Service Request from the LMC Support Portal at -
    http://www-947.ibm.com/support/entry/portal/Overview/Software/Lo
    tus/Lotus_Mobile_Connect . A PMR can also be opened via
    telephone at 800-IBM-SERV or for the phone number in your area
    please visit http://www.ibm.com/planetwide.
    

Comments

APAR Information

  • APAR number

    IZ74588

  • Reported component name

    LOTUS MOBILE CO

  • Reported component ID

    5724R2000

  • Reported release

    613

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-04-14

  • Closed date

    2010-08-20

  • Last modified date

    2010-08-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

    LOTUS MOBILE CO

  • Fixed component ID

    5724R2000

Applicable component levels

  • R610 PSN

       UP

  • R611 PSN

       UP

  • R612 PSN

       UP

  • R613 PSY

       UP

  • R614 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IBM Mobile Connect

Software version:

6.1.3

Reference #:

IZ74588

Modified date:

2010-08-20

Translate my page

Machine Translation

Content navigation