Service destroy immediately after execute sometimes results in cancelled jobs

Service destroy immediately after execute sometimes results in cancelled jobs

book

Article ID: KB0086742

calendar_today

Updated On:

Products Versions
TIBCO DataSynapse GridServer -
Not Applicable -

Description

Resolution:
If you execute a single task on a Service, then immediately call destroy, the Service may show up as cancelled from the GridServer Administration Tool. The workround is to call waitUntilInactive prior to destroy to guarantee that its state is completed rather than cancelled.

Issue/Introduction

Service destroy immediately after execute sometimes results in cancelled jobs