Petals SE EIP

The MONIT traces of the RoutingSlip are not correct

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 2.8.0
  • Fix Version/s: 2.8.2, 2.9.0
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    Using the RoutingSlip to invoke several services generates the following incorrect MONIT traces, at SE EIP level:

    ... traceCode = 'provideFlowStepBegin', flowInstanceId = 'a0575940-01cd-11e4-8e6d-0024e8ae9b85', flowStepId = 'a1048930-01cd-11e4-8e6d-0024e8ae9b85', flowStepInterfaceName = '{http://annudef.defense.gouv.fr/personneabstract/}personneabstract', flowStepServiceName = '{http://annudef.defense.gouv.fr/personne/}personne', flowStepOperationName = '{http://annudef.defense.gouv.fr/personneabstract/}infoPersonne', flowStepEndpointName = 'perEipEdp', flowPreviousStepId = 'a0578050-01cd-11e4-8e6d-0024e8ae9b85'
...
... here we will find correct MONIT traces about the first service invocation
...
... here after we will find incorrect MONIT traces, containing null values, about other services invocations
...
... traceCode = 'provideFlowStepBegin', flowInstanceId = null, flowStepId = null, flowStepInterfaceName = '{http://annudef.defense.gouv.fr/personneabstract/}dispatchPersonneResponse', flowStepServiceName = '{http://annudef.defense.gouv.fr/personne/}dispatchPersonneResponse', flowStepOperationName = '{http://annudef.defense.gouv.fr/personneabstract/}dispatchPersonneResponse', flowStepEndpointName = 'dispatchPersonneResponseEp', flowPreviousStepId = null
... traceCode = 'provideFlowStepBegin', flowInstanceId = null, flowStepId = null, flowStepInterfaceName = '{http://annudef.defense.gouv.fr/personneabstract/}dispatchPersonneResponseByMail', flowStepServiceName = '{http://annudef.defense.gouv.fr/personne/}dispatchPersonneResponseByMail', flowStepOperationName = '{http://annudef.defense.gouv.fr/personneabstract/}dispatchPersonneResponse', flowStepEndpointName = 'dispatchPersonneResponseByMailEp', flowPreviousStepId = null
... traceCode = 'provideFlowStepBegin', flowInstanceId = null, flowStepId = null, flowStepInterfaceName = '{http://annudef.defense.gouv.fr/personneabstract/}dispatchPersonneResponseByFtp', flowStepServiceName = '{http://annudef.defense.gouv.fr/personne/}dispatchPersonneResponseByFtp', flowStepOperationName = '{http://annudef.defense.gouv.fr/personneabstract/}dispatchPersonneResponse', flowStepEndpointName = 'dispatchPersonneResponseByFtpEp', flowPreviousStepId = null

    It seems that the flow context is not propagated to services providers except for the first one.

    Show
    Using the RoutingSlip to invoke several services generates the following incorrect MONIT traces, at SE EIP level: 
    ... traceCode = 'provideFlowStepBegin', flowInstanceId = 'a0575940-01cd-11e4-8e6d-0024e8ae9b85', flowStepId = 'a1048930-01cd-11e4-8e6d-0024e8ae9b85', flowStepInterfaceName = '{http://annudef.defense.gouv.fr/personneabstract/}personneabstract', flowStepServiceName = '{http://annudef.defense.gouv.fr/personne/}personne', flowStepOperationName = '{http://annudef.defense.gouv.fr/personneabstract/}infoPersonne', flowStepEndpointName = 'perEipEdp', flowPreviousStepId = 'a0578050-01cd-11e4-8e6d-0024e8ae9b85'
...
... here we will find correct MONIT traces about the first service invocation
...
... here after we will find incorrect MONIT traces, containing null values, about other services invocations
...
... traceCode = 'provideFlowStepBegin', flowInstanceId = null, flowStepId = null, flowStepInterfaceName = '{http://annudef.defense.gouv.fr/personneabstract/}dispatchPersonneResponse', flowStepServiceName = '{http://annudef.defense.gouv.fr/personne/}dispatchPersonneResponse', flowStepOperationName = '{http://annudef.defense.gouv.fr/personneabstract/}dispatchPersonneResponse', flowStepEndpointName = 'dispatchPersonneResponseEp', flowPreviousStepId = null
... traceCode = 'provideFlowStepBegin', flowInstanceId = null, flowStepId = null, flowStepInterfaceName = '{http://annudef.defense.gouv.fr/personneabstract/}dispatchPersonneResponseByMail', flowStepServiceName = '{http://annudef.defense.gouv.fr/personne/}dispatchPersonneResponseByMail', flowStepOperationName = '{http://annudef.defense.gouv.fr/personneabstract/}dispatchPersonneResponse', flowStepEndpointName = 'dispatchPersonneResponseByMailEp', flowPreviousStepId = null
... traceCode = 'provideFlowStepBegin', flowInstanceId = null, flowStepId = null, flowStepInterfaceName = '{http://annudef.defense.gouv.fr/personneabstract/}dispatchPersonneResponseByFtp', flowStepServiceName = '{http://annudef.defense.gouv.fr/personne/}dispatchPersonneResponseByFtp', flowStepOperationName = '{http://annudef.defense.gouv.fr/personneabstract/}dispatchPersonneResponse', flowStepEndpointName = 'dispatchPersonneResponseByFtpEp', flowPreviousStepId = null
    It seems that the flow context is not propagated to services providers except for the first one.
  • Environment:
    -

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Christophe DENEUX added a comment - Wed, 2 Jul 2014 - 12:07:00 +0200

Exact, the flow context is not propagated to the service providers except for the first one. The service provider are invoked asynchronously. When receiving the first asynchronous reply, the flow context should be repositionend from the reply.

Show
Christophe DENEUX added a comment - Wed, 2 Jul 2014 - 12:07:00 +0200 Exact, the flow context is not propagated to the service providers except for the first one. The service provider are invoked asynchronously. When receiving the first asynchronous reply, the flow context should be repositionend from the reply.
Hide
Permalink
Christophe DENEUX added a comment - Wed, 2 Jul 2014 - 14:35:38 +0200

Fixed in trunk

Show
Christophe DENEUX added a comment - Wed, 2 Jul 2014 - 14:35:38 +0200 Fixed in trunk
Hide
Permalink
Christophe DENEUX added a comment - Tue, 19 Aug 2014 - 10:30:16 +0200

Re-opened to be backported in branch petals-esb-enterprise-4.2.x

Show
Christophe DENEUX added a comment - Tue, 19 Aug 2014 - 10:30:16 +0200 Re-opened to be backported in branch petals-esb-enterprise-4.2.x
Hide
Permalink
Christophe DENEUX added a comment - Tue, 19 Aug 2014 - 11:02:21 +0200

Backported in branch petals-esb-enterprise-4.2.x

Show
Christophe DENEUX added a comment - Tue, 19 Aug 2014 - 11:02:21 +0200 Backported in branch petals-esb-enterprise-4.2.x

People

Dates

  • Created:
    Wed, 2 Jul 2014 - 12:04:59 +0200
    Updated:
    Tue, 19 Aug 2014 - 11:02:21 +0200
    Resolved:
    Tue, 19 Aug 2014 - 11:02:21 +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.