IT13085: AFTER UPGRADING STERLING B2B INTEGRATOR TO V5.2.6, A SUSTAINED CPU SPIKE IS ENCOUNTERED

APAR status

• Closed as program error.

Error description

• Sustained CPU spike, of the noapp process.  CPU spikes 30-40%
  higher than noted in previous builds in some cases.
  
  On Linux platforms this is captured with the "top" command.
  
  Using "top -H" (show threads) the offending thread within the
  noapp JVM was found to be a perimeter dispatcher thread.
  
  3XMTHREADINFO "Dispatcher" J9VMThread:0x00000000C1E87B00,
  j9thread_t:0x000000018384C580,
  java/lang/Thread:0x000000004814BED8, state:R, prio=5
  3XMJAVALTHREAD (java/lang/Thread getId:0x169, isDaemon:false)
  3XMTHREADINFO1 (native thread ID:0x49F0E1, native priority:0x5,
  native policy:UNKNOWN, vmstate:CW, vm thread flags:0x00000001)
  3XMCPUTIME CPU usage total: 343.139513000 secs, user:
  93.042105000 secs, system: 250.097408000 secs
  3XMHEAPALLOC Heap bytes allocated since last GC cycle=30243608
  (0x1CD7B18)
  3XMTHREADINFO3 Java callstack:
  4XESTACKTRACE at java/lang/Thread.sleep(Native Method)
  4XESTACKTRACE at
  java/lang/Thread.sleep(Thread.java:922(Compiled Code))
  4XESTACKTRACE at
  com/sterlingcommerce/perimeter/dispatcher/nio/NioDispatcher.bloc
  k(NioDispatcher.java:147(Compiled Code))
  4XESTACKTRACE at
  com/sterlingcommerce/perimeter/dispatcher/AbstractDispatcher.doR
  un(AbstractDispatcher.java:425(Compiled Code))
  4XESTACKTRACE at
  com/sterlingcommerce/perimeter/dispatcher/AbstractDispatcher$2.r
  un(AbstractDispatcher.java:175)
  4XESTACKTRACE at java/lang/Thread.run(Thread.java:798)
  
  This has been attributed to a parameter introduced into
  perimeter.properties:
  
  perimeter.niodispatcher=true
  
  Toggling this parameter to false drops the CPU back to normal
  levels.
  

Local fix

• STRRTC - 487243
  RW/RW
  Circumvention:
  Add the following to customer_overrides.properties:
  perimeter.perimeter.niodispatcher=false
  

Problem summary

• Users affected:
  All
  
  Problem Description:
  High CPU usage caused by Perimeter Dispatcher Thread
  property after upgrading to 5.2.6.
  
  Platforms Affected:
  All
  

Problem conclusion

• Resolution Summary:
  A code fix has been provided. For more information on changing
  the perimeter.niodispatcher.properties file to improve system
  performance in Glocal Mailbox, see Performace Overview in the
  Performace and tuning for Global Mailbox (V5.2.6 or later)
  documentation.
  
  Delivered in:
  5020601
  

Temporary fix

Comments

APAR Information

• 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

• R526 PSY

     UP