DoSelect SOAP Web Service Calls can cause suspended queries in Service Desk

Article Id: 109906
Status: Published
Updated On: 30-04-2019 07:13
Products:
SUPPORT AUTOMATION- SERVER CA Service Desk Manager - Unified Self Service KNOWLEDGE TOOLS CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager
Issue/Introduction:

After upgrading Service Desk to 17.1, DoSelect SOAP Web Service Calls can cause suspended queries in Service Desk. As a consequence Service Desk can become unresponsive because of many database agents getting busy.

See VDBINFO output below:

Agent #17 - (SEL) prov#6628_bpvirtdb_srvr @08/07/2018 09:47:49 with 1 in work
  SELECT_FULL (db_id=147383) SELECT call_req.open_date, call_req.id, call_req.ref_num, call_req.id FROM call_req ORDER BY call_req.open_date DESC
    SUSPENDED (10 of 10 recs) PROC(domsrvr) CNT(ServiceDesk)

DoSelect SOAP call example:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://www.ca.com/UnicenterServicePlus/ServiceDesk">
   <soapenv:Header/>
   <soapenv:Body>
      <ser:doSelect>
         <sid>1785083545</sid>
         <objectType>cr</objectType>
         <whereClause></whereClause>
         <maxRows>10</maxRows>
         <attributes>
            <string>ref_num</string>
            <string>status</string>
            <string>summary</string>
            <string>open_date</string>
            <string>resolve_date</string>
            <string>affected_service.name</string>
            <string>affected_service.system_name</string>
            <string>affected_service.asset_num</string>
            <string>affected_service.class</string>
            <string>affected_service.family</string>
            <string>affected_service.delete_flag</string>
            <string>assignee.last_name</string>
            <string>change.chg_ref_num</string>
            <string>group.last_name</string>
            <string>group.organization.name</string>
         </attributes>
      </ser:doSelect>
   </soapenv:Body>
</soapenv:Envelope>

Cause:

It is a known issue in Service Desk 17.1.

Environment:

CA Service Desk 17.1

Resolution:

There is a testfix available to be applied on top of Service Desk 17.1.
Make sure your environment runs Service Desk 17.1 and open a case at CA Support asking for the available testfix.

See details below:

PROB #: 0 FN: T52Y804 FT: D33 DATE: 25 Apr 2018 
PROBLEM SYMPTOM: WIN-MULTIPLE DOSELECT SOAP WEBSERVICE CALLS MAY RESULT IN CLIENT BECOMING UNRESPONSIVE

Additional Information:

The associated defect is DE39937. The solution to DE39937 is included in 17.1.0.1 ( https://docops.ca.com/ca-service-management/17-1/en/ca-service-management-17-1-0-1-release-notes/fixed-issues-17-1-0-1 )