IC89234: BPMONITOR CAUSES NPE WHEN BEING WATCHED FOR A LONG TIME OVER SLOW NETWORK CONNECTION

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

  • BPMonitor causes NPE when being watched for a long time over
    slow network connection
    OOM is caused because of piling up of Session Objects
    maintained in Jetty code in the HashMap. Each Session object is
    created as part of the HTTP request and response request coming
    through the SI and Web browser...
    Customer indicated that they were experiencing the slow network
    in the web browser..
    
    Because of slowness in network, these objects were piled up and
    caused the OOM in SI system..
    
    We are confirmed that there is no memory leak in the SI/jetty
    code in the area.
    
    Current page access was causing NPE exception, because of the
    OOM caused. Session object was null , accessing this object
    while processing current page was causing NPE.
    

Local fix

  • STRRTC - 358429
    CM/CM
    Circumvention: None
    

Problem summary

  • Users Affected:
    All system having slowness on Web brower, accessing the BP
    Monitor page
    
    Problem Description:
    BPMonitor causes NPE when being watched for a long time over
    slow network connection
    OOM is caused because of piling up of Session Objects maintained
    in Jetty code in the HashMap.
    Each Session object is created as part of the HTTP request and
    response request coming
    through the SI and Web browser...
    Customer indicated that they were experiencing the slow network
    in the web browser..
    
      Platforms Affected:
    All
    

Problem conclusion

  • Because of slowness in network, these objects were piled up and
    caused the OOM in SI system..
    We are confirmed that there is no memory leak in the SI/jetty
    coe in the area.
    Current page access was causing NPE exception, because of the
    OOM caused. Session object was null , accessing this object
    while processing current page was causing NPE.
    
     Resolution Summary:
    Added a NPE logic on BP monitor code to not to throw the
    exception
    
    Delivered In:
    5020403
    

Temporary fix

Comments

  • Waiting for review
    

APAR Information

  • APAR number

    IC89234

  • Reported component name

    STR B2B INTEGRA

  • Reported component ID

    5725D0600

  • Reported release

    522

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-12-20

  • Closed date

    2013-01-01

  • Last modified date

    2013-01-01

  • 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

    STR B2B INTEGRA

  • Fixed component ID

    5725D0600

Applicable component levels

  • R524 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

Sterling B2B Integrator

Software version:

5.2.2

Reference #:

IC89234

Modified date:

2013-01-01

Translate my page

Machine Translation

Content navigation