IBM Support

PI76866: OUTBOUND GATEWAY OOM

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.

Direct links to fixes

3.0.0.15-FTM-CPS-MP-iFix0006
3.0.0.15-FTM-Check-MP-iFix0006
3.0.0.15-FTM-ACH-MP-iFix0006

 

APAR status

  • Closed as program error.

Error description

  • The heapdump has the following signature:
2,220,002,528 (99.62%) [24] 1 java/util/Vector 0x5097f748
|- 2,220,002,504 (99.62%) [83,886,096] 12,135,575 array of
java/lang/Object 0xbb7e7728
   |- 200 (0%) [24] 1 java/lang/String 0x64d48578
   |- 192 (0%) [24] 1 java/lang/String 0x83ceaab0
   |- 192 (0%) [24] 1 java/lang/String 0x83ce0328

From the javacore:

"OutgoingFileLocator" J9VMThread:0x3A367E00,
j9thread_t:0x3A4EEC0C, java/lang/Thread:0x509610E0, state:R,
prio=5
3XMJAVALTHREAD            (java/lang/Thread getId:0x3D,
isDaemon:false)
3XMTHREADINFO1            (native thread ID:0x4B027B, native
priority:0x5, native policy:UNKNOWN, vmstate:R, vm thread
flags:0x00000020)
3XMCPUTIME               CPU usage total: 242.897757000 secs,
user: 81.020072000 secs, system: 161.877685000 secs
3XMHEAPALLOC             Heap bytes allocated since last GC
cycle=83886088 (0x5000008)
3XMTHREADINFO3           Java callstack:
4XESTACKTRACE                at
java/util/Arrays.copyOf(Arrays.java:2453(Compiled Code))
4XESTACKTRACE                at
java/util/Arrays.copyOf(Arrays.java:2427(Compiled Code))
4XESTACKTRACE                at
java/util/Vector.grow(Vector.java:274(Compiled Code))
4XESTACKTRACE                at
java/util/Vector.ensureCapacityHelper(Vector.java:254(Compiled
Code))
4XESTACKTRACE                at
java/util/Vector.add(Vector.java:790(Compiled Code))
5XESTACKTRACE                   (entered lock:
java/util/Vector@0x5097FF60, entry count: 1)
4XESTACKTRACE                at
com/ibm/icpcs/gatewayserver/filereceive/OutgoingFileLocator.lock
Files(OutgoingFileLocator.java:318(Compiled Code))
4XESTACKTRACE                at
com/ibm/icpcs/gatewayserver/filereceive/OutgoingFileLocator.run(
OutgoingFileLocator.java:150)
4XESTACKTRACE                at
java/lang/Thread.run(Thread.java:798)

Local fix

  • Switch to a 64-bit JVM for the outbound gateway.  set the Xmx to
4Gb and restart the Gateway daily

Problem summary

  • 



Problem conclusion


    

  • Prevent infinite loop in inbound and outound file locators that
were preventing gateway threads from pausing and allowing local
vectors to live indefinitely. Also prevent vectors from
accumulating file of the same name.

    



Temporary fix


    

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    PI76866
    • 

  • Reported component name
    CHECK SERVICES
    • 

  • Reported component ID
    5725S7730
    • 

  • Reported release
    300
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2017-02-20
    • 

  • Closed date
    2017-03-02
    • 

  • Last modified date
    2017-03-02
    • 





    

  • 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
    CHECK SERVICES
    • 

  • Fixed component ID
    5725S7730
    • 



Applicable component levels


    

  • R300  PSN
       UP
    • 








      
              
                            

              

              [{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3HMA","label":"IBM Financial Transaction Manager for Check Services"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            14 August 2020
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback