Random warning "Could not find the context xyz" using tRunJob

[Sebastien2]

Hello,

The message "Could not find the context xyz" appears randomly on our different work environments (Default, DEV, PREPROD, PROD).

We then observe that the default values of the child Job are lost, any value is set to null

The randomness of this phenomenon is a real problem
How can this happen? How to solve it?

To reproduce it, perform a large number of iterations on a tRunJob and produce a simple "println" of the context values from the child job.

Here is an example of the console output (println from child Job) :
context.context_asstring is a string set to "prod" by default into child Job.
context.parent_value is a blank string by default into child Job but the string "parent_value" is transmitted from parent Job.

[statistics] connecting to socket on port 3518
[statistics] connected
2019-09-09 14:25:52.116 : 0000001 | contextStr = PROD | context.context_asstring = prod | context.parent_value = parent_value
2019-09-09 14:25:52.229 : 0000002 | contextStr = PROD | context.context_asstring = prod | context.parent_value = parent_value
2019-09-09 14:25:52.330 : 0000003 | contextStr = PROD | context.context_asstring = prod | context.parent_value = parent_value
2019-09-09 14:25:52.431 : 0000004 | contextStr = PROD | context.context_asstring = prod | context.parent_value = parent_value
2019-09-09 14:25:52.535 : 0000005 | contextStr = PROD | context.context_asstring = prod | context.parent_value = parent_value
2019-09-09 14:25:52.636 : 0000006 | contextStr = PROD | context.context_asstring = prod | context.parent_value = parent_value
2019-09-09 14:25:52.736 : 0000007 | contextStr = PROD | context.context_asstring = prod | context.parent_value = parent_value
2019-09-09 14:25:52.838 : 0000008 | contextStr = PROD | context.context_asstring = prod | context.parent_value = parent_value
2019-09-09 14:25:52.938 : 0000009 | contextStr = PROD | context.context_asstring = prod | context.parent_value = parent_value
2019-09-09 14:25:53.390 : 0000010 | contextStr = PROD | context.context_asstring = prod | context.parent_value = parent_value
(...)
2019-09-09 14:39:00.410 : 0007813 | contextStr = PROD | context.context_asstring = null | context.parent_value = parent_value
Could not find the context PROD
2019-09-09 14:39:00.141 : 0007814 | contextStr = PROD | context.context_asstring = null | context.parent_value = parent_value
Could not find the context PROD
2019-09-09 14:39:00.242 : 0007815 | contextStr = PROD | context.context_asstring = null | context.parent_value = parent_value
Could not find the context PROD
2019-09-09 14:39:00.342 : 0007816 | contextStr = PROD | context.context_asstring = null | context.parent_value = parent_value
Could not find the context PROD
Could not find the context PROD
2019-09-09 14:39:00.447 : 0007817 | contextStr = PROD | context.context_asstring = null | context.parent_value = parent_value
2019-09-09 14:39:00.557 : 0007818 | contextStr = PROD | context.context_asstring = null | context.parent_value = parent_value
Could not find the context PROD
2019-09-09 14:39:00.669 : 0007819 | contextStr = PROD | context.context_asstring = null | context.parent_value = parent_value
Could not find the context PROD
Could not find the context PROD
2019-09-09 14:39:00.791 : 0007820 | contextStr = PROD | context.context_asstring = null | context.parent_value = parent_value
Could not find the context PROD
2019-09-09 14:39:00.936 : 0007821 | contextStr = PROD | context.context_asstring = null | context.parent_value = parent_value
2019-09-09 14:39:01.510 : 0007822 | contextStr = PROD | context.context_asstring = null | context.parent_value = parent_value
Could not find the context PROD
(...)

Talend Studio 6.3.1.1.20180108_0814-patch
Java version 1.8.0_191-b12 (x64)

Regards ,

[Anonymous]

Hello,

Can you please clarify in which Talend version/edition you are? Are you using talend open studio or subscription solution?

Best regards

Sabrina

[Sebastien2]

Hello,

We use Talend Studio 6.3.1.1.20180108_0814-patch and Java version 1.8.0_191-b12 (x64)

At the same time, we opened a ticket with the support team.

Regards,