"CLOSING" status on Requests tab in Studio manager
Article ID: KB0079942
Updated On:
| Products | Versions |
|---|---|
| TIBCO Data Virtualization | TDV All Versions |
Description
This is information on on "CLOSING" status under Requests tab in Studio manager when request is running for long time and the status is not changed.
Issue/Introduction
This is information on on "CLOSING" status under Requests tab in Studio manager when request is running for long time and the status is not changed.
Resolution
This behavior is by design where requests are in closing status provided by Product team.
The status "CLOSING" simply means that TDV has made the request to Cancel/Close the request to that underlying database driver. However the underlying database (Source datasource) may not necessarily successfully honor that request. or it may honor it but fail to acknowledge that it did.
Any request that TDV shows in CLOSING status is not using any TDV resources. It's only shown there to let you know that even though TDV has closed the request on it's side: The underlying database may not have successfully terminated the request on *its* side. By leaving the request in the table with a CLOSING status this gives admins the knowledge they need to go and investigate Source database to make sure the request there is truly closed.
Since the requests with CLOSING status take up no resources within TDV, they do no harm to TDV by continuing to exist in the requests table. There's no need to remove them or to restart TDV to get rid of them.
The status "CLOSING" simply means that TDV has made the request to Cancel/Close the request to that underlying database driver. However the underlying database (Source datasource) may not necessarily successfully honor that request. or it may honor it but fail to acknowledge that it did.
Any request that TDV shows in CLOSING status is not using any TDV resources. It's only shown there to let you know that even though TDV has closed the request on it's side: The underlying database may not have successfully terminated the request on *its* side. By leaving the request in the table with a CLOSING status this gives admins the knowledge they need to go and investigate Source database to make sure the request there is truly closed.
Since the requests with CLOSING status take up no resources within TDV, they do no harm to TDV by continuing to exist in the requests table. There's no need to remove them or to restart TDV to get rid of them.
Feedback
Yes
No
Powered by
