After force uninstalling and deleting an HTTP Connector Resource Instance and deleting the Shared Resource, the HTTP Connector Resource Instance is still present in the tibcohost describeDeployedConnectors command output on that node.

After force uninstalling and deleting an HTTP Connector Resource Instance and deleting the Shared Resource, the HTTP Connector Resource Instance is still present in the tibcohost describeDeployedConnectors command output on that node.

book

Article ID: KB0093239

calendar_today

Updated On:

Products Versions
TIBCO ActiveMatrix Service Grid -
Not Applicable -

Description

Resolution:
The HTTP Connector Resource Instance can still be present if the HTTP Connector Resource Instance is deleted from the AMX Administrator Database but is still present in the  runtime. In this scenario you cannot delete it from the Administrator UI as the HTTP Connector Resource Instance is no longer visible from the Administrator UI.

A workaround to remove the problematic Resource Instance follows. Note that "force delete" of a Resource Instance is a high impact task and normally should only be done with TIBCO Support / Engineering supervision.

1). On the same node, recreate the RI (same name and same template).

2). Click "Install". The RI would be shown as running (ignore Action History in case it is shown as Failed).

3). Uninstall and delete the RI from the Administrator UI. Check the node logs for any error.

4). Verify using the tibcohost describeDeployedConnectors command.

Issue/Introduction

After force uninstalling and deleting an HTTP Connector Resource Instance and deleting the Shared Resource, the HTTP Connector Resource Instance is still present in the tibcohost describeDeployedConnectors command output on that node.