Petals Distribution

Improve the identification of the service endpoint initiating a timeout

Details

  • Type: Improvement Request Improvement Request
  • Status: In Progress In Progress
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 5.2.0, CP-5.2.0
  • Fix Version/s: 5.2.1, CP-5.2.1, 5.3.1, CP-5.3.1
  • Component/s: Components
  • Security Level: Public
  • Description:
    Hide

    When a timeout occurs it could be difficult to identify which service endpoint is too slow and initiates a timeout without enabling fine log traces.

    With a log configuration limited to level 'INFO', we have following traces:

    • at level 'MONIT': it is a trace explaining why the processing fails without identifying the service endpoint initiating the timeout 
      petals-05-node-1 2022/11/16 09:47:40,838 GMT+0100 MONIT [Petals.Container.Components.petals-se-camel.su-camel-bordereau-provide-1.2] :  traceCode = 'provideFlowStepFailure', flowInstanceId = '2d0ed640-658b-11ed-b338-005056a2c4e5', flowStepId = '2da83010-658b-11ed-b338-005056a2c4e5', failureMessage = 'A timeout happened while Camel sent an exchange to a JBI service', dumpFile = './flow-monitoring/2d0ed640-658b-11ed-b338-005056a2c4e5/2da83010-658b-11ed-b338-005056a2c4e5_provideFlowStepFailure.log'
    • at level 'WARNING': traces are component-dependent

    For all components, please add a trace with level 'WARNING', identifying clearly the invoked service operation and the flow step associated to service consumer, as following:

    2024/02/27 16:53:05,389 GMT+0100 WARNING [org.ow2.petals.component.framework.UnderTestWithDefaultConf] : A timeout expired (10000 ms) sending a message to a service provider ({http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverService|edpArchiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverShortSync) in the context of the flow step '41c656d0-d588-11ee-96b8-024200dc0afc/41c656d1-d588-11ee-96b8-024200dc0afc'

    For each binding component providing service consumer, update the failure trace with level 'MONIT' to identify clearly the invoked service operation and the flow step associated to service consumer, as following:

    2024/02/28 12:19:19,512 GMT+0100 MONIT [org.ow2.petals.component.framework.UnderTestWithDefaultConf] :  traceCode = 'consumeExtFlowStepFailure', flowInstanceId = '333a4a60-d62b-11ee-9e2e-024200dc0afc', flowStepId = '333a4a61-d62b-11ee-9e2e-024200dc0afc', failureMessage = 'A timeout expired (5000 ms) sending a message to a service provider ({http://testProvideService}testProvideInterfaceName|{http://testProvideService}testServiceName|testEndpointName|{http://petals.ow2.org/components/filetransfer/version-5}put) in the context of the flow step '333a4a60-d62b-11ee-9e2e-024200dc0afc/333a4a61-d62b-11ee-9e2e-024200dc0afc''

    For each service engine invoking service consumer, improve the error message returned to its service consume to identify clearly the invoked service operation and the flow step associated to service consumer, as following:

    A timeout expired (5000 ms) sending a message to a service provider ({http://testProvideService}testProvideInterfaceName|{http://testProvideService}testServiceName|testEndpointName|{http://petals.ow2.org/components/filetransfer/version-5}put) in the context of the flow step '333a4a60-d62b-11ee-9e2e-024200dc0afc/333a4a61-d62b-11ee-9e2e-024200dc0afc'
    Show
    When a timeout occurs it could be difficult to identify which service endpoint is too slow and initiates a timeout without enabling fine log traces. With a log configuration limited to level 'INFO', we have following traces:
    • at level 'MONIT': it is a trace explaining why the processing fails without identifying the service endpoint initiating the timeout 
      petals-05-node-1 2022/11/16 09:47:40,838 GMT+0100 MONIT [Petals.Container.Components.petals-se-camel.su-camel-bordereau-provide-1.2] :  traceCode = 'provideFlowStepFailure', flowInstanceId = '2d0ed640-658b-11ed-b338-005056a2c4e5', flowStepId = '2da83010-658b-11ed-b338-005056a2c4e5', failureMessage = 'A timeout happened while Camel sent an exchange to a JBI service', dumpFile = './flow-monitoring/2d0ed640-658b-11ed-b338-005056a2c4e5/2da83010-658b-11ed-b338-005056a2c4e5_provideFlowStepFailure.log'
    • at level 'WARNING': traces are component-dependent
    For all components, please add a trace with level 'WARNING', identifying clearly the invoked service operation and the flow step associated to service consumer, as following: 
    2024/02/27 16:53:05,389 GMT+0100 WARNING [org.ow2.petals.component.framework.UnderTestWithDefaultConf] : A timeout expired (10000 ms) sending a message to a service provider ({http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverService|edpArchiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverShortSync) in the context of the flow step '41c656d0-d588-11ee-96b8-024200dc0afc/41c656d1-d588-11ee-96b8-024200dc0afc'
    For each binding component providing service consumer, update the failure trace with level 'MONIT' to identify clearly the invoked service operation and the flow step associated to service consumer, as following: 
    2024/02/28 12:19:19,512 GMT+0100 MONIT [org.ow2.petals.component.framework.UnderTestWithDefaultConf] :  traceCode = 'consumeExtFlowStepFailure', flowInstanceId = '333a4a60-d62b-11ee-9e2e-024200dc0afc', flowStepId = '333a4a61-d62b-11ee-9e2e-024200dc0afc', failureMessage = 'A timeout expired (5000 ms) sending a message to a service provider ({http://testProvideService}testProvideInterfaceName|{http://testProvideService}testServiceName|testEndpointName|{http://petals.ow2.org/components/filetransfer/version-5}put) in the context of the flow step '333a4a60-d62b-11ee-9e2e-024200dc0afc/333a4a61-d62b-11ee-9e2e-024200dc0afc''
    For each service engine invoking service consumer, improve the error message returned to its service consume to identify clearly the invoked service operation and the flow step associated to service consumer, as following: 
    A timeout expired (5000 ms) sending a message to a service provider ({http://testProvideService}testProvideInterfaceName|{http://testProvideService}testServiceName|testEndpointName|{http://petals.ow2.org/components/filetransfer/version-5}put) in the context of the flow step '333a4a60-d62b-11ee-9e2e-024200dc0afc/333a4a61-d62b-11ee-9e2e-024200dc0afc'
  • Environment:
    -

Issue Links

Depends
 

Activity

Ascending order - Click to sort in descending order
Christophe DENEUX made changes - Wed, 28 Feb 2024 - 11:07:40 +0100
Field Original Value New Value
Status New [ 10000 ] Open [ 10002 ]
Priority Major [ 3 ]
Christophe DENEUX made changes - Wed, 28 Feb 2024 - 11:07:43 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Christophe DENEUX made changes - Wed, 28 Feb 2024 - 11:11:19 +0100
Link This issue depends on PETALSCDK-210 [ PETALSCDK-210 ]
Christophe DENEUX made changes - Wed, 28 Feb 2024 - 11:36:37 +0100
Link This issue depends on PETALSSEFLOWABLE-93 [ PETALSSEFLOWABLE-93 ]
Christophe DENEUX made changes - Wed, 28 Feb 2024 - 12:04:45 +0100
Description When a timeout occurs it could be difficult to identify which service endpoint is too slow and initiates a timeout without enabling fine log traces.

With a log configuration limited to level '{{INFO}}', we have following traces:
* at level 'MONIT': it is a trace explaining why the processing fails without identifying the service endpoint initiating the timeout
{code}
petals-05-node-1 2022/11/16 09:47:40,838 GMT+0100 MONIT [Petals.Container.Components.petals-se-camel.su-camel-bordereau-provide-1.2] : traceCode = 'provideFlowStepFailure', flowInstanceId = '2d0ed640-658b-11ed-b338-005056a2c4e5', flowStepId = '2da83010-658b-11ed-b338-005056a2c4e5', failureMessage = 'A timeout happened while Camel sent an exchange to a JBI service', dumpFile = './flow-monitoring/2d0ed640-658b-11ed-b338-005056a2c4e5/2da83010-658b-11ed-b338-005056a2c4e5_provideFlowStepFailure.log'
{code}
* at level 'WARNING': traces are component-dependent

Please add a trace with level '{{WARNING}}', identifying clearly the invoked service operation and the flow step associated to service consumer, as following:
{code}
2024/02/27 16:53:05,389 GMT+0100 WARNING [org.ow2.petals.component.framework.UnderTestWithDefaultConf] : A timeout expired (10000 ms) sending a message to a service provider ({http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverService|edpArchiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverShortSync) in the context of the flow step '41c656d0-d588-11ee-96b8-024200dc0afc/41c656d1-d588-11ee-96b8-024200dc0afc'
{code} 		When a timeout occurs it could be difficult to identify which service endpoint is too slow and initiates a timeout without enabling fine log traces.

With a log configuration limited to level '{{INFO}}', we have following traces:
* at level 'MONIT': it is a trace explaining why the processing fails without identifying the service endpoint initiating the timeout
{code}
petals-05-node-1 2022/11/16 09:47:40,838 GMT+0100 MONIT [Petals.Container.Components.petals-se-camel.su-camel-bordereau-provide-1.2] : traceCode = 'provideFlowStepFailure', flowInstanceId = '2d0ed640-658b-11ed-b338-005056a2c4e5', flowStepId = '2da83010-658b-11ed-b338-005056a2c4e5', failureMessage = 'A timeout happened while Camel sent an exchange to a JBI service', dumpFile = './flow-monitoring/2d0ed640-658b-11ed-b338-005056a2c4e5/2da83010-658b-11ed-b338-005056a2c4e5_provideFlowStepFailure.log'
{code}
* at level 'WARNING': traces are component-dependent

For all components, please add a trace with level '{{WARNING}}', identifying clearly the invoked service operation and the flow step associated to service consumer, as following:
{code}
2024/02/27 16:53:05,389 GMT+0100 WARNING [org.ow2.petals.component.framework.UnderTestWithDefaultConf] : A timeout expired (10000 ms) sending a message to a service provider ({http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverService|edpArchiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverShortSync) in the context of the flow step '41c656d0-d588-11ee-96b8-024200dc0afc/41c656d1-d588-11ee-96b8-024200dc0afc'
{code}

For each binding component providing service consumer, update the failure trace with level '{{MONIT}}' to identify clearly the invoked service operation and the flow step associated to service consumer, as following:
{code}
2024/02/27 16:53:05,389 GMT+0100 WARNING [org.ow2.petals.component.framework.UnderTestWithDefaultConf] : A timeout expired (10000 ms) sending a message to a service provider ({http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverService|edpArchiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverShortSync) in the context of the flow step '41c656d0-d588-11ee-96b8-024200dc0afc/41c656d1-d588-11ee-96b8-024200dc0afc'
{code}
Christophe DENEUX made changes - Wed, 28 Feb 2024 - 12:05:19 +0100
Description When a timeout occurs it could be difficult to identify which service endpoint is too slow and initiates a timeout without enabling fine log traces.

With a log configuration limited to level '{{INFO}}', we have following traces:
* at level 'MONIT': it is a trace explaining why the processing fails without identifying the service endpoint initiating the timeout
{code}
petals-05-node-1 2022/11/16 09:47:40,838 GMT+0100 MONIT [Petals.Container.Components.petals-se-camel.su-camel-bordereau-provide-1.2] : traceCode = 'provideFlowStepFailure', flowInstanceId = '2d0ed640-658b-11ed-b338-005056a2c4e5', flowStepId = '2da83010-658b-11ed-b338-005056a2c4e5', failureMessage = 'A timeout happened while Camel sent an exchange to a JBI service', dumpFile = './flow-monitoring/2d0ed640-658b-11ed-b338-005056a2c4e5/2da83010-658b-11ed-b338-005056a2c4e5_provideFlowStepFailure.log'
{code}
* at level 'WARNING': traces are component-dependent

For all components, please add a trace with level '{{WARNING}}', identifying clearly the invoked service operation and the flow step associated to service consumer, as following:
{code}
2024/02/27 16:53:05,389 GMT+0100 WARNING [org.ow2.petals.component.framework.UnderTestWithDefaultConf] : A timeout expired (10000 ms) sending a message to a service provider ({http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverService|edpArchiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverShortSync) in the context of the flow step '41c656d0-d588-11ee-96b8-024200dc0afc/41c656d1-d588-11ee-96b8-024200dc0afc'
{code}

For each binding component providing service consumer, update the failure trace with level '{{MONIT}}' to identify clearly the invoked service operation and the flow step associated to service consumer, as following:
{code}
2024/02/27 16:53:05,389 GMT+0100 WARNING [org.ow2.petals.component.framework.UnderTestWithDefaultConf] : A timeout expired (10000 ms) sending a message to a service provider ({http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverService|edpArchiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverShortSync) in the context of the flow step '41c656d0-d588-11ee-96b8-024200dc0afc/41c656d1-d588-11ee-96b8-024200dc0afc'
{code} 		When a timeout occurs it could be difficult to identify which service endpoint is too slow and initiates a timeout without enabling fine log traces.

With a log configuration limited to level '{{INFO}}', we have following traces:
* at level 'MONIT': it is a trace explaining why the processing fails without identifying the service endpoint initiating the timeout
{code}
petals-05-node-1 2022/11/16 09:47:40,838 GMT+0100 MONIT [Petals.Container.Components.petals-se-camel.su-camel-bordereau-provide-1.2] : traceCode = 'provideFlowStepFailure', flowInstanceId = '2d0ed640-658b-11ed-b338-005056a2c4e5', flowStepId = '2da83010-658b-11ed-b338-005056a2c4e5', failureMessage = 'A timeout happened while Camel sent an exchange to a JBI service', dumpFile = './flow-monitoring/2d0ed640-658b-11ed-b338-005056a2c4e5/2da83010-658b-11ed-b338-005056a2c4e5_provideFlowStepFailure.log'
{code}
* at level 'WARNING': traces are component-dependent

*For all components*, please add a trace with level '{{WARNING}}', identifying clearly the invoked service operation and the flow step associated to service consumer, as following:
{code}
2024/02/27 16:53:05,389 GMT+0100 WARNING [org.ow2.petals.component.framework.UnderTestWithDefaultConf] : A timeout expired (10000 ms) sending a message to a service provider ({http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverService|edpArchiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverShortSync) in the context of the flow step '41c656d0-d588-11ee-96b8-024200dc0afc/41c656d1-d588-11ee-96b8-024200dc0afc'
{code}

*For each binding component providing service consumer*, update the failure trace with level '{{MONIT}}' to identify clearly the invoked service operation and the flow step associated to service consumer, as following:
{code}
2024/02/27 16:53:05,389 GMT+0100 WARNING [org.ow2.petals.component.framework.UnderTestWithDefaultConf] : A timeout expired (10000 ms) sending a message to a service provider ({http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverService|edpArchiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverShortSync) in the context of the flow step '41c656d0-d588-11ee-96b8-024200dc0afc/41c656d1-d588-11ee-96b8-024200dc0afc'
{code}
Christophe DENEUX made changes - Wed, 28 Feb 2024 - 12:20:09 +0100
Description When a timeout occurs it could be difficult to identify which service endpoint is too slow and initiates a timeout without enabling fine log traces.

With a log configuration limited to level '{{INFO}}', we have following traces:
* at level 'MONIT': it is a trace explaining why the processing fails without identifying the service endpoint initiating the timeout
{code}
petals-05-node-1 2022/11/16 09:47:40,838 GMT+0100 MONIT [Petals.Container.Components.petals-se-camel.su-camel-bordereau-provide-1.2] : traceCode = 'provideFlowStepFailure', flowInstanceId = '2d0ed640-658b-11ed-b338-005056a2c4e5', flowStepId = '2da83010-658b-11ed-b338-005056a2c4e5', failureMessage = 'A timeout happened while Camel sent an exchange to a JBI service', dumpFile = './flow-monitoring/2d0ed640-658b-11ed-b338-005056a2c4e5/2da83010-658b-11ed-b338-005056a2c4e5_provideFlowStepFailure.log'
{code}
* at level 'WARNING': traces are component-dependent

*For all components*, please add a trace with level '{{WARNING}}', identifying clearly the invoked service operation and the flow step associated to service consumer, as following:
{code}
2024/02/27 16:53:05,389 GMT+0100 WARNING [org.ow2.petals.component.framework.UnderTestWithDefaultConf] : A timeout expired (10000 ms) sending a message to a service provider ({http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverService|edpArchiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverShortSync) in the context of the flow step '41c656d0-d588-11ee-96b8-024200dc0afc/41c656d1-d588-11ee-96b8-024200dc0afc'
{code}

*For each binding component providing service consumer*, update the failure trace with level '{{MONIT}}' to identify clearly the invoked service operation and the flow step associated to service consumer, as following:
{code}
2024/02/27 16:53:05,389 GMT+0100 WARNING [org.ow2.petals.component.framework.UnderTestWithDefaultConf] : A timeout expired (10000 ms) sending a message to a service provider ({http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverService|edpArchiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverShortSync) in the context of the flow step '41c656d0-d588-11ee-96b8-024200dc0afc/41c656d1-d588-11ee-96b8-024200dc0afc'
{code} 		When a timeout occurs it could be difficult to identify which service endpoint is too slow and initiates a timeout without enabling fine log traces.

With a log configuration limited to level '{{INFO}}', we have following traces:
* at level 'MONIT': it is a trace explaining why the processing fails without identifying the service endpoint initiating the timeout
{code}
petals-05-node-1 2022/11/16 09:47:40,838 GMT+0100 MONIT [Petals.Container.Components.petals-se-camel.su-camel-bordereau-provide-1.2] : traceCode = 'provideFlowStepFailure', flowInstanceId = '2d0ed640-658b-11ed-b338-005056a2c4e5', flowStepId = '2da83010-658b-11ed-b338-005056a2c4e5', failureMessage = 'A timeout happened while Camel sent an exchange to a JBI service', dumpFile = './flow-monitoring/2d0ed640-658b-11ed-b338-005056a2c4e5/2da83010-658b-11ed-b338-005056a2c4e5_provideFlowStepFailure.log'
{code}
* at level 'WARNING': traces are component-dependent

*For all components*, please add a trace with level '{{WARNING}}', identifying clearly the invoked service operation and the flow step associated to service consumer, as following:
{code}
2024/02/27 16:53:05,389 GMT+0100 WARNING [org.ow2.petals.component.framework.UnderTestWithDefaultConf] : A timeout expired (10000 ms) sending a message to a service provider ({http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverService|edpArchiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverShortSync) in the context of the flow step '41c656d0-d588-11ee-96b8-024200dc0afc/41c656d1-d588-11ee-96b8-024200dc0afc'
{code}

*For each binding component providing service consumer*, update the failure trace with level '{{MONIT}}' to identify clearly the invoked service operation and the flow step associated to service consumer, as following:
{code}
2024/02/28 12:19:19,512 GMT+0100 MONIT [org.ow2.petals.component.framework.UnderTestWithDefaultConf] : traceCode = 'consumeExtFlowStepFailure', flowInstanceId = '333a4a60-d62b-11ee-9e2e-024200dc0afc', flowStepId = '333a4a61-d62b-11ee-9e2e-024200dc0afc', failureMessage = 'A timeout expired (5000 ms) sending a message to a service provider ({http://testProvideService}testProvideInterfaceName|{http://testProvideService}testServiceName|testEndpointName|{http://petals.ow2.org/components/filetransfer/version-5}put) in the context of the flow step '333a4a60-d62b-11ee-9e2e-024200dc0afc/333a4a61-d62b-11ee-9e2e-024200dc0afc''
{code}
Christophe DENEUX made changes - Wed, 28 Feb 2024 - 12:56:24 +0100
Link This issue depends on PETALSBCFTRANS-89 [ PETALSBCFTRANS-89 ]
Christophe DENEUX made changes - Wed, 28 Feb 2024 - 12:58:51 +0100
Link This issue depends on PETALSBCFTRANS-90 [ PETALSBCFTRANS-90 ]
Christophe DENEUX made changes - Wed, 28 Feb 2024 - 13:04:04 +0100
Link This issue depends on PETALSCDK-211 [ PETALSCDK-211 ]
Christophe DENEUX made changes - Wed, 28 Feb 2024 - 13:14:15 +0100
Link This issue depends on PETALSBCJBI-23 [ PETALSBCJBI-23 ]
Christophe DENEUX made changes - Wed, 28 Feb 2024 - 13:15:27 +0100
Link This issue depends on PETALSBCJBI-24 [ PETALSBCJBI-24 ]
Christophe DENEUX made changes - Wed, 28 Feb 2024 - 13:18:22 +0100
Link This issue blocks PETALSBCREST-121 [ PETALSBCREST-121 ]
Christophe DENEUX made changes - Wed, 28 Feb 2024 - 13:19:12 +0100
Link This issue blocks PETALSBCREST-121 [ PETALSBCREST-121 ]
Christophe DENEUX made changes - Wed, 28 Feb 2024 - 13:19:18 +0100
Link This issue depends on PETALSBCREST-121 [ PETALSBCREST-121 ]
Christophe DENEUX made changes - Wed, 28 Feb 2024 - 13:56:52 +0100
Link This issue depends on PETALSBCREST-122 [ PETALSBCREST-122 ]
Christophe DENEUX made changes - Wed, 28 Feb 2024 - 16:46:13 +0100
Link This issue depends on PETALSBCSOAP-240 [ PETALSBCSOAP-240 ]
Christophe DENEUX made changes - Wed, 28 Feb 2024 - 17:40:41 +0100
Link This issue depends on PETALSBCSOAP-241 [ PETALSBCSOAP-241 ]
Christophe DENEUX made changes - Thu, 29 Feb 2024 - 10:03:30 +0100
Link This issue depends on PETALSBCMAIL-67 [ PETALSBCMAIL-67 ]
Christophe DENEUX made changes - Thu, 29 Feb 2024 - 10:06:43 +0100
Link This issue depends on PETALSBCMAIL-68 [ PETALSBCMAIL-68 ]
Christophe DENEUX made changes - Thu, 29 Feb 2024 - 10:33:20 +0100
Link This issue depends on PETALSSEQUARTZ-35 [ PETALSSEQUARTZ-35 ]
Christophe DENEUX made changes - Thu, 29 Feb 2024 - 10:35:56 +0100
Link This issue depends on PETALSSEQUARTZ-36 [ PETALSSEQUARTZ-36 ]
Christophe DENEUX made changes - Thu, 29 Feb 2024 - 13:58:00 +0100
Link This issue depends on PETALSSECAMEL-55 [ PETALSSECAMEL-55 ]
Christophe DENEUX made changes - Thu, 29 Feb 2024 - 13:59:30 +0100
Link This issue depends on PETALSSECAMEL-56 [ PETALSSECAMEL-56 ]
Christophe DENEUX made changes - Thu, 29 Feb 2024 - 14:00:47 +0100
Affects Version/s CP-5.2.0 [ 10838 ]
Affects Version/s 5.2.0 [ 10837 ]
Affects Version/s CP-5.3.0 [ 10909 ]
Affects Version/s 5.3.0 [ 10908 ]
Christophe DENEUX made changes - Thu, 29 Feb 2024 - 15:34:59 +0100
Link This issue depends on PETALSSEPOJO-38 [ PETALSSEPOJO-38 ]
Christophe DENEUX made changes - Thu, 29 Feb 2024 - 16:03:42 +0100
Link This issue depends on PETALSSEPOJO-39 [ PETALSSEPOJO-39 ]
Christophe DENEUX made changes - Fri, 1 Mar 2024 - 09:57:27 +0100
Link This issue depends on PETALSSEMAPPING-10 [ PETALSSEMAPPING-10 ]
Christophe DENEUX made changes - Fri, 1 Mar 2024 - 10:26:02 +0100
Link This issue depends on PETALSSEMAPPING-11 [ PETALSSEMAPPING-11 ]
Christophe DENEUX made changes - Mon, 4 Mar 2024 - 09:15:21 +0100
Description When a timeout occurs it could be difficult to identify which service endpoint is too slow and initiates a timeout without enabling fine log traces.

With a log configuration limited to level '{{INFO}}', we have following traces:
* at level 'MONIT': it is a trace explaining why the processing fails without identifying the service endpoint initiating the timeout
{code}
petals-05-node-1 2022/11/16 09:47:40,838 GMT+0100 MONIT [Petals.Container.Components.petals-se-camel.su-camel-bordereau-provide-1.2] : traceCode = 'provideFlowStepFailure', flowInstanceId = '2d0ed640-658b-11ed-b338-005056a2c4e5', flowStepId = '2da83010-658b-11ed-b338-005056a2c4e5', failureMessage = 'A timeout happened while Camel sent an exchange to a JBI service', dumpFile = './flow-monitoring/2d0ed640-658b-11ed-b338-005056a2c4e5/2da83010-658b-11ed-b338-005056a2c4e5_provideFlowStepFailure.log'
{code}
* at level 'WARNING': traces are component-dependent

*For all components*, please add a trace with level '{{WARNING}}', identifying clearly the invoked service operation and the flow step associated to service consumer, as following:
{code}
2024/02/27 16:53:05,389 GMT+0100 WARNING [org.ow2.petals.component.framework.UnderTestWithDefaultConf] : A timeout expired (10000 ms) sending a message to a service provider ({http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverService|edpArchiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverShortSync) in the context of the flow step '41c656d0-d588-11ee-96b8-024200dc0afc/41c656d1-d588-11ee-96b8-024200dc0afc'
{code}

*For each binding component providing service consumer*, update the failure trace with level '{{MONIT}}' to identify clearly the invoked service operation and the flow step associated to service consumer, as following:
{code}
2024/02/28 12:19:19,512 GMT+0100 MONIT [org.ow2.petals.component.framework.UnderTestWithDefaultConf] : traceCode = 'consumeExtFlowStepFailure', flowInstanceId = '333a4a60-d62b-11ee-9e2e-024200dc0afc', flowStepId = '333a4a61-d62b-11ee-9e2e-024200dc0afc', failureMessage = 'A timeout expired (5000 ms) sending a message to a service provider ({http://testProvideService}testProvideInterfaceName|{http://testProvideService}testServiceName|testEndpointName|{http://petals.ow2.org/components/filetransfer/version-5}put) in the context of the flow step '333a4a60-d62b-11ee-9e2e-024200dc0afc/333a4a61-d62b-11ee-9e2e-024200dc0afc''
{code} 		When a timeout occurs it could be difficult to identify which service endpoint is too slow and initiates a timeout without enabling fine log traces.

With a log configuration limited to level '{{INFO}}', we have following traces:
* at level 'MONIT': it is a trace explaining why the processing fails without identifying the service endpoint initiating the timeout
{code}
petals-05-node-1 2022/11/16 09:47:40,838 GMT+0100 MONIT [Petals.Container.Components.petals-se-camel.su-camel-bordereau-provide-1.2] : traceCode = 'provideFlowStepFailure', flowInstanceId = '2d0ed640-658b-11ed-b338-005056a2c4e5', flowStepId = '2da83010-658b-11ed-b338-005056a2c4e5', failureMessage = 'A timeout happened while Camel sent an exchange to a JBI service', dumpFile = './flow-monitoring/2d0ed640-658b-11ed-b338-005056a2c4e5/2da83010-658b-11ed-b338-005056a2c4e5_provideFlowStepFailure.log'
{code}
* at level 'WARNING': traces are component-dependent

*For all components*, please add a trace with level '{{WARNING}}', identifying clearly the invoked service operation and the flow step associated to service consumer, as following:
{code}
2024/02/27 16:53:05,389 GMT+0100 WARNING [org.ow2.petals.component.framework.UnderTestWithDefaultConf] : A timeout expired (10000 ms) sending a message to a service provider ({http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverService|edpArchiver|{http://petals.ow2.org/se-flowable/unit-test/timeout-on-service/archivageService}archiverShortSync) in the context of the flow step '41c656d0-d588-11ee-96b8-024200dc0afc/41c656d1-d588-11ee-96b8-024200dc0afc'
{code}

*For each binding component providing service consumer*, update the failure trace with level '{{MONIT}}' to identify clearly the invoked service operation and the flow step associated to service consumer, as following:
{code}
2024/02/28 12:19:19,512 GMT+0100 MONIT [org.ow2.petals.component.framework.UnderTestWithDefaultConf] : traceCode = 'consumeExtFlowStepFailure', flowInstanceId = '333a4a60-d62b-11ee-9e2e-024200dc0afc', flowStepId = '333a4a61-d62b-11ee-9e2e-024200dc0afc', failureMessage = 'A timeout expired (5000 ms) sending a message to a service provider ({http://testProvideService}testProvideInterfaceName|{http://testProvideService}testServiceName|testEndpointName|{http://petals.ow2.org/components/filetransfer/version-5}put) in the context of the flow step '333a4a60-d62b-11ee-9e2e-024200dc0afc/333a4a61-d62b-11ee-9e2e-024200dc0afc''
{code}

*For each service engine invoking service consumer*, improve the error message returned to its service consume to identify clearly the invoked service operation and the flow step associated to service consumer, as following:
{code}
A timeout expired (5000 ms) sending a message to a service provider ({http://testProvideService}testProvideInterfaceName|{http://testProvideService}testServiceName|testEndpointName|{http://petals.ow2.org/components/filetransfer/version-5}put) in the context of the flow step '333a4a60-d62b-11ee-9e2e-024200dc0afc/333a4a61-d62b-11ee-9e2e-024200dc0afc'
{code}
Christophe DENEUX made changes - Mon, 4 Mar 2024 - 09:16:21 +0100
Link This issue depends on PETALSSEMAPPING-12 [ PETALSSEMAPPING-12 ]
Christophe DENEUX made changes - Mon, 4 Mar 2024 - 09:18:11 +0100
Link This issue depends on PETALSSECAMEL-57 [ PETALSSECAMEL-57 ]
Christophe DENEUX made changes - Mon, 4 Mar 2024 - 09:58:35 +0100
Link This issue depends on PETALSSEFLOWABLE-94 [ PETALSSEFLOWABLE-94 ]
Christophe DENEUX made changes - Wed, 6 Mar 2024 - 09:57:03 +0100
Link This issue depends on PETALSBCJBI-25 [ PETALSBCJBI-25 ]
Christophe DENEUX made changes - Fri, 15 Mar 2024 - 12:52:46 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 5.2.1 [ 11190 ]
Fix Version/s CP-5.2.1 [ 11191 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Fri, 15 Mar 2024 - 12:53:05 +0100
Status Resolved [ 10004 ] Open [ 10002 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Fri, 15 Mar 2024 - 12:53:09 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Christophe DENEUX made changes - Fri, 15 Mar 2024 - 12:53:23 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 5.3.1 [ 11208 ]
Fix Version/s CP-5.3.1 [ 11209 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Fri, 15 Mar 2024 - 12:54:42 +0100
Status Resolved [ 10004 ] Open [ 10002 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Fri, 15 Mar 2024 - 12:54:45 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Christophe DENEUX made changes - Fri, 15 Mar 2024 - 13:19:25 +0100
Link This issue depends on PETALSSEASE-22 [ PETALSSEASE-22 ]
Christophe DENEUX made changes - Fri, 15 Mar 2024 - 13:23:28 +0100
Link This issue depends on PETALSSEASE-23 [ PETALSSEASE-23 ]
Christophe DENEUX made changes - Fri, 15 Mar 2024 - 17:55:00 +0100
Link This issue depends on PETALSSEEIP-40 [ PETALSSEEIP-40 ]

People

Dates

  • Created:
    Wed, 28 Feb 2024 - 11:07:30 +0100
    Updated:
    Fri, 15 Mar 2024 - 17:55:00 +0100
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.