Petals log handlers use only the flow log data of the current thread context to compute the right log file in which log event must be flushed.
In few use case, this does not work correctly: when a new flow is created from a step of a current flow, we are able to create the right flow log data for each flow and we are able to transmit the right information to the logging system, but only the context (so, the one of the current flow) is used to retrieve the log file.
So, Petals log handler must use the flow log data transmitted through the log event. If no flow log data is available, the context will be use to retrieve the required information:
on MONIT level, the flow log data exists always
on other log level, no flow log data exists, the context will be used.
Petals log handlers use only the flow log data of the current thread context to compute the right log file in which log event must be flushed.
In few use case, this does not work correctly: when a new flow is created from a step of a current flow, we are able to create the right flow log data for each flow and we are able to transmit the right information to the logging system, but only the context (so, the one of the current flow) is used to retrieve the log file.
So, Petals log handler must use the flow log data transmitted through the log event. If no flow log data is available, the context will be use to retrieve the required information:
on MONIT level, the flow log data exists always
on other log level, no flow log data exists, the context will be used.
Christophe DENEUX added a comment - Tue, 14 Apr 2015 - 14:16:05 +0200 Fixed in trunk through svn#37093. Assertions about flow instance identifier value must be added.
Christophe DENEUX added a comment - Wed, 15 Apr 2015 - 17:44:11 +0200 Backported from trunk into petals-4.3.x by svn#37118 , including assertions about flow attributes. Assertions must be merged in trunk
Fixed in trunk through svn#37093. Assertions about flow instance identifier value must be added.