PI21521: SIPSESSION LEAKS IN B2B APPLICATION WHEN THERE IS DOWNSTREAM FORKING

8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• User UserA calls user UserB.  User UserB has 2 devices
  registered with a downstream proxy.
  
  INVITE in
  SAS local.xxxx created
  SS created local.xxxx_1604_1
  B2B app creates outgoing INVITE request
  SS created  local.xxxx_1605_1
  INVITE out to downstream proxy, from-tag yyyy.xxxx_1605
  ** At this point the B2B app has 1 SAS local.xxxx with these SS:
   - local.xxxx_1604_1 -session from caller-B2B
   - local.xxxx_1605_1 -session from B2B-callee
  
  recv 180 to-tag 58a7b418_TUserBaaa.bbb.ccc.ddd
  recv 180 to-tag 6d7d9300_TUserBaaa.bbb.ccc.eee
  SS local.xxxx_1608_1 created
  ** At this point the B2B app has 1 SAS local.xxxx with these SS:
   - local.xxxx_1604_1 -session from caller-B2B
   - local.xxxx_1605_1 -session from B2B-callee-to tag.20
   - local.xxxx_1608_1 -session from B2B-callee-to tag.84
  
  send 180 to-tag gggg_local.xxxx_1604
  SS local.xxxx_1609_1 created
  send 180 to-tag gggg_local.xxxx_1609.
  ** At this point the B2B app has 1 SAS local.xxxx with these SS:
   - local.xxxx_1604_1 -session from caller-B2B-to-tag_1604
   - local.xxxx_1609_1 -session from caller-B2B-to-tag_1609
   - local.xxxx_1605_1 -session from B2B-callee-to tag.20
   - local.xxxx_1608_1 -session from B2B-callee-to tag.84
  
  
  recv 200 to-tag hhhhh-6d7d9300_TUserBaaa.bbb.ccc.eee
  send 200 to-tag iiii_local.xxxx_1609
  sent
  ACK rcvd
  Retransmission of 200 OK to-tag
  hhhhh-6d7d9300_TUserBaaa.bbb.ccc.eee
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: SIPSESSION LEAKS IN B2B APP WHEN THERE  *
  *                      IS                                      *
  *                      DOWNSTREAM FORKING                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  1.Trying to reuse underlying transacion while it's in method
  terminateUnderlyingTransaction causes exception.
  2.Invalidation of SipApplicationSession doesn't invalidate all
  SipSession in case of IncomingDeadSipRequest in the caller leg.
  

Problem conclusion

• 1. Adding member _underlyingTransactionsBeingTerminated to
  TransactionUserImpl that indicates not to reuse transaction.
  2. check before calling terminateUnderlyingTransaction method
  that the request isn't type of IncomingDeadSipRequest
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.4.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R850 PSY

     UP