Community
Participate
Working Groups
If a pipelet uses external resources, for example a database connection, and the operation takes too long, so the whole pipline is aborted due to a timeout of the pipeline. The database connection isn't released. So it would be better if the pipelet has a clean up method to free the resources after the timeout. This method must be called after the timeout. But it must prevent a dead end meaning the clean up method can also take a long time (but shouldn't). So a new time for the clean up method would be necessary.
Sounds sensible. However we would have to find a way to detect that the pipelet was aborted by a pipeline timeout and to notify a pipelet in an affected thread about it. I need to do some investigation about it ...
