2284055 - Locked login causing many spids in MAINTENANCE TOKEN and error 1601 in error log - SAP ASE

• sp_who shows loginame as NULL and cmd in MAINTENANCE TOKEN  for thousands of logins:   

fid spid status      loginame   origname   hostname   blk_spid dbname      tempdbname  cmd               block_xloid threadpool
--- ---- ----------- ---------- ---------- -------------- -------- ----------- ----------- ----------------- ----------- ----------------
   0   17 sleeping    NULL       NULL        bs041         0 master      master      MAINTENANCE TOKEN           0 NULL
   0   18 sleeping    NULL       NULL        bs039         0 master      master      MAINTENANCE TOKEN           0 NULL
   0   19 sleeping    NULL       NULL        bs040         0 master      master      MAINTENANCE TOKEN           0 NULL
   0   20 sleeping    NULL       NULL        bs038         0 master      master      MAINTENANCE TOKEN           0 NULL
   0   21 sleeping    NULL       NULL        bs038         0 master      master      MAINTENANCE TOKEN           0 NULL
(...deleted for brevity...)

• The only login for the hosts shown is locked.  
   
• The errorlog has thousands of Error 1601:

Error: 1601, Severity: 17, State: 3
There are not enough 'user connections' available to start a new process. Retry when there are fewer active users, or ask your System Administrator to reconfigure ASE with more user connections.  

• CPU usage is near 100%.

• SAP Adaptive Server Enterprise (ASE) 15.x
• SAP Adaptive Server Enterprise (ASE) 16.0

authentication, engine , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , How To