Petals ESB Container

Petals log handler must use flow log data of the MONIT trace when exists

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 4.2.4
  • Fix Version/s: 4.3.0
  • Component/s: Logging
  • Security Level: Public
  • Description:
    Hide

    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.
    Show
    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.
  • Environment:
    -

Activity

Ascending order - Click to sort in descending order
Christophe DENEUX made changes - Mon, 13 Apr 2015 - 11:38:56 +0200
Field Original Value New Value
Priority Blocker [ 1 ]
Description 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. 		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 made changes - Mon, 13 Apr 2015 - 11:39:03 +0200
Status New [ 10000 ] Open [ 10002 ]
Priority Blocker [ 1 ] Major [ 3 ]
Christophe DENEUX made changes - Mon, 13 Apr 2015 - 11:39:06 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Hide
Permalink
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.

Show
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 made changes - Tue, 14 Apr 2015 - 14:17:46 +0200
Fix Version/s 4.3.0 [ 10542 ]
Fix Version/s 5.0.0 [ 10413 ]
Christophe DENEUX made changes - Tue, 14 Apr 2015 - 14:20:23 +0200
Link This issue depends on PETALSDISTRIB-116 [ PETALSDISTRIB-116 ]
Christophe DENEUX made changes - Wed, 15 Apr 2015 - 17:40:24 +0200
Comment [ To be merged in branch petals-4.3.x, assertions about flow instance identifier value require the backport of PETALSDISTRIB-116 ]
Christophe DENEUX made changes - Wed, 15 Apr 2015 - 17:41:19 +0200
Link This issue depends on PETALSDISTRIB-116 [ PETALSDISTRIB-116 ]
Hide
Permalink
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

Show
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
Hide
Permalink
Christophe DENEUX added a comment - Wed, 15 Apr 2015 - 18:12:56 +0200

Assertions about flow attributes merged in trunk by svn#37119

Show
Christophe DENEUX added a comment - Wed, 15 Apr 2015 - 18:12:56 +0200 Assertions about flow attributes merged in trunk by svn#37119
Christophe DENEUX made changes - Wed, 15 Apr 2015 - 18:13:07 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Thu, 21 May 2015 - 10:24:14 +0200
Fix Version/s 5.0.0 [ 10413 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
1m 3s
1
Christophe DENEUX
Mon, 13 Apr 2015 - 11:39:03 +0200
Open Open In Progress In Progress
3s
1
Christophe DENEUX
Mon, 13 Apr 2015 - 11:39:06 +0200
In Progress In Progress Resolved Resolved
2d 6h 34m
1
Christophe DENEUX
Wed, 15 Apr 2015 - 18:13:07 +0200



People

Dates

  • Created:
    Mon, 13 Apr 2015 - 11:38:00 +0200
    Updated:
    Thu, 21 May 2015 - 10:24:14 +0200
    Resolved:
    Wed, 15 Apr 2015 - 18:13:07 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.