0000964: Father job dies even if the error was catched in the child job

Viewing Issue Advanced Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0000964

[Talend Open Studio] Perl components

feature

N/A

2007-04-17 07:43

2008-01-15 16:57

Reporter

mmercier

View Status

public

Assigned To

Priority

normal

Resolution

fixed

Platform

Status

closed

Projection

none

OS Version

ETA

none

Fixed in Version

2.3.0M2

Product Version

2.0.0RC1

Target Version

Product Build

Summary

0000964: Father job dies even if the error was catched in the child job

Description

When an error occurs in a subjob (i.e. a job called via a tRunJob component), the subjob dies, even if the error is catched using a "onError" trigger (the kind of error tested was a DB connection to a non-existent DB or table). Then the parent job dies too, and its parent too(if any) and so on, until the "root" job dies. It should be possible to catch an error and treat it localy, in such a way that the parent job wouldn't even need to be notified of that error, or at least wouldn't die.

Steps To Reproduce

An simple exemple of such "cascading dying jobs" can be found in the forum [Forum] topic 545

Additional Information

Tags

No tags attached.

generated language

workload (in half days)

Attached Files

Relationships

related to	0000935	closed	rbillerey	management of the ErrorCode of the tRunJob when the childJob die
related to	0002319	closed		[tRunJob] new option "die on child error"

Notes
(0004786) plegall (reporter) 2007-10-22 18:23	After discussion with smallet and fbonan, we agree with your request: if the error was catched in the child job, father job should not consider child as "on error".

(0005720) plegall (reporter) 2007-12-13 18:04	If the error was catched with an OnError link in the child job, the tRunJob in the father job won't go into OnError link because we consider it has already been managed in the child job. Fixed on trunk in [Subversion, tos] r7594

Issue History
Date Modified	Username	Field	Change
2007-04-17 07:43	mmercier	New Issue
2007-04-17 08:52	plegall	Steps to Reproduce Updated
2007-04-24 02:35	ccarbone	Assigned To	=> plegall
2007-04-24 02:35	ccarbone	Status	new => feedback from Talend
2007-08-31 12:08	plegall	Relationship added	related to 0000935
2007-10-22 16:38	plegall	Relationship added	related to 0002319
2007-10-22 18:23	plegall	Note Added: 0004786
2007-10-22 18:24	plegall	Status	feedback from Talend => assigned
2007-10-22 18:24	plegall	Summary	When an error occurs in a subjob, both jobs (parent job and subjob) die, even if the error is treated in the subjob => Father job dies even if the error was catched in the child job
2007-12-13 18:04	plegall	Note Added: 0005720
2007-12-13 18:04	plegall	Status	assigned => resolved/needs doc
2007-12-13 18:04	plegall	Resolution	open => fixed
2007-12-13 18:04	plegall	Fixed in Version	=> 2.3.0M2
2008-01-15 16:57	plegall	Status	resolved/needs doc => closed

Mantis 1.1.6[^]