PH52502: PARSING BAD SIP REQUESTS/RESPONSES CAN LEAD TO HIGH CPU

APAR status

• Closed as program error.

Error description

• Parsing bad SIP requests/responses can lead to high CPU.  The
  javacore shows high CPU in threads running SIP Container code
  with multiple "Default" threads running code like:
  
  "Default : 2" J9VMThread:0x0000000002373000,
  omrthread_t:0x0000558221961120,
  java/lang/Thread:0x00000006E3DAAB20, state:R, prio=5
  CPU usage total: 17497.163249043 secs, current
  category="Application"
  Java callstack:
  at java/util/Hashtable.get(Hashtable.java:414(Compiled Code))
    (entered lock: java/util/Properties@0x00000006E19ABB40, entry
  count: 1)
  at com/ibm/ws/sip/properties/SipPropertiesMap.getBoolean(SipPro
  pertiesMap.java:296(CompiledCode))
  at com/ibm/ws/sip/parser/MessageParser.parseStartLine(MessagePa
  rser.java:186(CompiledCode))
  at com/ibm/ws/sip/parser/StreamMessageParser.parse(StreamMessag
  eParser.java:132(CompiledCode))
  at com/ibm/ws/sip/stack/transaction/transport/TransportCommLaye
  rMgr.onRead(TransportCommLayerMgr.java:1259(CompiledCode))
  at com/ibm/ws/sip/stack/dispatch/Dispatcher.queueIncomingDataEv
  ent(Dispatcher.java:279(CompiledCode))
  at com/ibm/ws/sip/stack/transaction/transport/connections/chann
  elframework/BaseConnection.messageReceived(BaseConnection.java:
  98(CompiledCode))
  at com/ibm/ws/sip/stack/transaction/transport/connections/chann
  elframework/SipConnLink.complete(SipConnLink.java:512(CompiledCo
  at com/ibm/ws/sip/stack/transaction/transport/connections/chann
  elframework/SipInboundConnLink.complete(SipInboundConnLink.java
  :98)
  at com/ibm/ws/sip/stack/transaction/transport/connections/chann
  elframework/SipConnLink.connectionEstablished(SipConnLink.java:
  168)
  at com/ibm/ws/sip/stack/transaction/transport/connections/chann
  elframework/SipInboundConnLink.init(SipInboundConnLink.java:63)
  at com/ibm/ws/sip/stack/transaction/transport/connections/chann
  elframework/SipInboundConnLink.ready(SipInboundConnLink.java:79)
    (entered lock: com/ibm/ws/sip/stack/transaction/transport/con
  nections/channelframework/SipTcpInboundConnLink@0x00000007297F9
  BC8,entry count: 1)
  at com/ibm/ws/tcp/channel/impl/NewConnectionInitialReadCallback
  .sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
  at com/ibm/ws/tcp/channel/impl/NewConnectionInitialReadCallback
  .complete(NewConnectionInitialReadCallback.java:113)
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server who are setting the sipcontainer     *
  *                  custom property                             *
  *                  number.of.parse.errors.allowed to           *
  *                  any other value than 0                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Parsing badly formatted SIP requests    *
  *                      can                                     *
  *                      lead to increased CPU usage and slow    *
  *                      performance.                            *
  ****************************************************************
  * RECOMMENDATION:  Setting sipcontainer custom property to     *
  *                  number.of.parse.errors.allowed to the value *
  *                  0 will prevent this issue from happening.   *
  *                  If customer needs                           *
  *                  number.of.parse.errors.allowed              *
  *                  set to any other value than 0 then          *
  *                  installing the iFix will help.              *
  ****************************************************************
  When the sipcontainer is trying to parse a badly formatted SIP
  request it does not stop parsing the message when an error is
  encountered, it keeps trying to parse it. This behavior results
  in increased CPU usage and lower performance.
  

Problem conclusion

• The fix for this APAR is targeted for inclusion in fix packs
  8.5.5.24 and 9.0.5.16. vFor more information, see
  'Recommended Updates for WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels