000021427 - How to clear persistent established Administrative and Runtime API socket connections from DCOM Bridge-based client sessions in RSA ClearTrust

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000021427
Applies ToRSA ClearTrust 5.5.2 Administrative DCOM API
RSA ClearTrust 5.5.2 Runtime DCOM API
Microsoft Windows 2000 Server SP4
IssueHow to clear persistent established Administrative and Runtime API socket connections from DCOM Bridge-based client sessions in RSA ClearTrust
At the conclusion of an ASP that establishes an Administrative or Runtime API connection, a socket to the respective API server remains allocated. As more and more instances of the ASP are invoked, eventually the client or server exhausts its available sockets. Running netstat -a, sockets connections for port 5601 (default Admin API server), and/or port 5615 (default Runtime API server) accumulate.
CauseCommon VBScript practice for cleaning up at the conclusion of processing is to reset variables to nothing, or null value. This, however, does not close the open socket connection to the respective API server.
ResolutionAt the conclusion of ASP processing, the proper corresponding API method must be invoked to explicitly close the socket established for the API connection. For Administrative API connections, this is the APIServerProxy.disconnect() method. For Runtime API connections, this is the RuntimeAPI.close() method.
Legacy Article IDa22861

Attachments

    Outcomes