Guest

Preview Tool

Cisco Bug: CSCvu61796 - XCP Authentication Cores when invoking Multi-threading in IMS

Last Modified

Oct 19, 2020

Products (2)

  • Cisco Unified Communications Manager IM & Presence Service
  • Cisco Unified Communications Manager IM and Presence Service Version 12.5

Known Affected Releases

12.5(1)

Description (partial)

Symptom:
Core Dumps are observed for XCP Authentication Service
This can impact Jabber login if the service doesn't automatically recover

Conditions:
IM&P 12.5.1 Su2
Issue is observed when SSO is enabled, however, it may occur when SSO isn't enabled as well

Reviewing the Crash Stack:

crash has occured while trying to access ssoCacheMap.
#7 operator[]<stlp_std::basic_string<char, stlp_std::char_traits<char>, stlp_std::allocator<char> > > (
__k=spy:string("hostname.domain", size: 32), this=0x5676ed58 <AuthenticationImpl::ssoCacheMap>)
at /data/BLD-cup_su2_12_5_1-git-d/tpl/release/include/stlport/stl/_map.h:176
#8 AuthenticationImpl::executeCurl (this=0xf3648000, curl=0xf1e00c68, http_code=http_code@entry=0xf3647a88,
hostname=spy:string("hostname.domain", size: 32), cacheCookies=cacheCookies@entry=true) at AuthenticationImpl.cpp:603
On further analyzing the backtrace could see that we have around 3 threads that has invoked AuthenticationImpl
thread 32
#26 0xf76b88fe in curl_easy_perform () from /usr/local/cm/lib/libcurl_cisco.so.4
#27 0x5666c3b8 in AuthenticationImpl::executeCurl (this=0xf374a000, curl=0xf303d260, http_code=http_code@entry=0xf3749a88,
hostname=spy:string("hostname.domain", size: 32), cacheCookies=cacheCookies@entry=false) at AuthenticationImpl.cpp:595
#28 0x5666d959 in AuthenticationImpl::OAuth_Validate (this=this@entry=0xf374a000, access_token=<optimized out>, loginResultSSO=...)
at AuthenticationImpl.cpp:790
#29 0x56652d04 in SXComponent::authenticateOauthToken (this=this@entry=0x578a6a80, text=text@entry=0xf1c3c950 "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6IjNlM2FkNWYzLTZkZjItNDc0MC1hNzI4LWNjODUxMDJlZTI2MzpmNzI1ZjVkNjQ1MjUzOGI3NjE0NmUzNDIzNzdkZmE5MWUyNDI1OTZhZTA2ZjEyNWMxZTUwNzU0OGE0MGJjODcxIn0.eyJwcml2YXRlIjoi"..., loginResultSSO=..., reason=@0xf374a0e8: DEFAULT) at SXComponent.cpp:1058
#30 0x56653dce in SXComponent::_processRequest (this=0x578a6a80, conn=0x57ca3b30, e=0xf2965c30) at SXComponent.cpp:540
thread 26
#8 stlp_std::priv::_Rb_tree<stlp_std::basic_string<char, stlp_std::char_traits<char>, stlp_std::allocator<char> >, stlp_std::less<stlp_std::basic_string<char, stlp_std::char_traits<char>, stlp_std::allocator<char> > >, stlp_std::pair<stlp_std::basic_string<char, stlp_std::char_traits<char>, stlp_std::allocator<char> > const, stlp_std::basic_string<char, stlp_std::char_traits<char>, stlp_std::allocator<char> > >, stlp_std::priv::_Select1st<stlp_std::pair<stlp_std::basic_string<char, stlp_std::char_traits<char>, stlp_std::allocator<char> > const, stlp_std::basic_string<char, stlp_std::char_traits<char>, stlp_std::allocator<char> > > >, stlp_std::priv::_MapTraitsT<stlp_std::pair<stlp_std::basic_string<char, stlp_std::char_traits<char>, stlp_std::allocator<char> > const, stlp_std::basic_string<char, stlp_std::char_traits<char>, stlp_std::allocator<char> > > >, stlp_std::allocator<stlp_std::pair<stlp_std::basic_string<char, stlp_std::char_traits<char>, stlp_std::allocator<char> > const, stlp_std::basic_string<char, stlp_std::char_traits<char>, stlp_std::allocator<char> > > > >::_M_erase (this=this@entry=0x5676ed58 <AuthenticationImpl::ssoCacheMap>, __x=0xf3046980)
at /data/BLD-cup_su2_12_5_1-git-d/tpl/release/include/stlport/stl/_tree.c:661
#9 0x5666da9c in clear (this=0x5676ed58 <AuthenticationImpl::ssoCacheMap>) at /data/BLD-cup_su2_12_5_1-git-d/tpl/release/include/stlport/stl/_tree.h:536
#10 clear (this=0x5676ed58 <AuthenticationImpl::ssoCacheMap>) at /data/BLD-cup_su2_12_5_1-git-d/tpl/release/include/stlport/stl/_map.h:206
#11 AuthenticationImpl::OAuth_Validate (this=this@entry=0xf37cb000, access_token=<optimized out>, loginResultSSO=...) at AuthenticationImpl.cpp:820
#12 0x56652d04 in SXComponent::authenticateOauthToken (this=this@entry=0x578a6a80, text=text@entry=0xf1c2bfd8 "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6IjNlM2FkNWYzLTZkZjItNDc0MC1hNzI4LWNjODUxMDJlZTI2MzpmNzI1ZjVkNjQ1MjUzOGI3NjE0NmUzNDIzNzdkZmE5MWUyNDI1OTZhZTA2ZjEyNWMxZTUwNzU0OGE0MGJjODcxIn0.eyJwcml2YXRlIjoi"..., loginResultSSO=..., reason=@0xf37cb0e8: DEFAULT) at SXComponent.cpp:1058
#13 0x56653dce in SXComponent::_processRequest (this=0x578a6a80, conn=0x57ca3b30, e=0xf2819ff8) at SXComponent.cpp:540
thread 1
#7 operator[]<stlp_std::basic_string<char, stlp_std::char_traits<char>, stlp_std::allocator<char> > > (
__k=spy:string("hostname.domain", size: 32), this=0x5676ed58 <AuthenticationImpl::ssoCacheMap>)
at /data/BLD-cup_su2_12_5_1-git-d/tpl/release/include/stlport/stl/_map.h:176
#8 AuthenticationImpl::executeCurl (this=0xf3648000, curl=0xf1e00c68, http_code=http_code@entry=0xf3647a88,
hostname=spy:string("hostname.domain", size: 32), cacheCookies=cacheCookies@entry=true) at AuthenticationImpl.cpp:603
#9 0x5666d959 in AuthenticationImpl::OAuth_Validate (this=this@entry=0xf3648000, access_token=<optimized out>, loginResultSSO=...)
at AuthenticationImpl.cpp:790
#10 0x56652d04 in SXComponent::authenticateOauthToken (this=this@entry=0x578a6a80,
text=text@entry=0xf1c08188 "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6IjNlM2FkNWYzLTZkZjItNDc0MC1hNzI4LWNjODUxMDJlZTI2MzpmNzI1ZjVkNjQ1MjUzOGI3NjE0NmUzNDIzNzdkZmE5MWUyNDI1OTZhZTA2ZjEyNWMxZTUwNzU0OGE0MGJjODcxIn0.eyJwcml2YXRlIjoi"..., loginResultSSO=..., reason=@0xf36480e8: DEFAULT) at SXComponent.cpp:1058
#11 0x56653dce in SXComponent::_processRequest (this=0x578a6a80, conn=0x57ca3b30, e=0xf29892d0) at SXComponent.cpp:540

As shown above, thread 1 is trying to access ssoCacheMap, whereas in thread 26 the ssoCacheMap is cleared by invoking ssoCacheMap.clear();
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.