[#PETALSCDK-210] Add a log trace identifying clearly the invoked service operation initiating a timeout - Petals Link JIRA

Details

Type: Improvement Request
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: 5.7.0, 5.8.0
Fix Version/s: 5.7.2, 5.8.1
Component/s: runtime
Security Level: Public

Description:

Hide

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'

Show

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'

Environment:

-

Issue Links

Depends

This issue blocks:
PETALSSEEIP-40 A warning log trace identifying clearly the invoked service operation initiating a timeout is not generated
~~PETALSSEFLOWABLE-93~~ A warning log trace identifying clearly the invoked service operation initiating a timeout is not generated
~~PETALSBCFTRANS-89~~ A warning log trace identifying clearly the invoked service operation initiating a timeout is not generated
~~PETALSBCJBI-23~~ A warning log trace identifying clearly the invoked service operation initiating a timeout is not generated
~~PETALSBCREST-121~~ A warning log trace identifying clearly the invoked service operation initiating a timeout is not generated
~~PETALSBCMAIL-67~~ A warning log trace identifying clearly the invoked service operation initiating a timeout is not generated
~~PETALSSEQUARTZ-35~~ A warning log trace identifying clearly the invoked service operation initiating a timeout is not generated
~~PETALSSECAMEL-55~~ A warning log trace identifying clearly the invoked service operation initiating a timeout is not generated
~~PETALSSEPOJO-38~~ A warning log trace identifying clearly the invoked service operation initiating a timeout is not generated
~~PETALSSEASE-22~~ A warning log trace identifying clearly the invoked service operation initiating a timeout is not generated
PETALSDISTRIB-587 Improve the identification of the service endpoint initiating a timeout
PETALSSEASE-23 Improve the JMS error returned on timeout to identify clearly the invoked service operation and the flow step associated to service consumer
~~PETALSBCSOAP-241~~ Improve the SOAP fault returned on timeout to identify clearly the invoked service operation and the flow step associated to service consumer
~~PETALSSEMAPPING-10~~ Improve the warning log trace about a service operation initiating a timeout

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Christophe DENEUX added a comment - Wed, 28 Feb 2024 - 11:30:22 +0100

A log trace is added on both method:
'AbstractListener.sendSync(...)' used to send synchronously messages to service provider,
'AbstractJBIListener.onExpiredAsyncJBIMessage()' used to process request message sent asynchronously to service provider. As this method is overridden at component level, it is needed to check that the default implementation is invoked with 'super.onExpiredAsyncJBIMessage(asyncExchange, asyncContext)'.

A unit test should be added at component level to verify the right processing of timeout, including this log trace.

Show

Christophe DENEUX added a comment - Wed, 28 Feb 2024 - 11:30:22 +0100 A log trace is added on both method: 'AbstractListener.sendSync(...)' used to send synchronously messages to service provider, 'AbstractJBIListener.onExpiredAsyncJBIMessage()' used to process request message sent asynchronously to service provider. As this method is overridden at component level, it is needed to check that the default implementation is invoked with 'super.onExpiredAsyncJBIMessage(asyncExchange, asyncContext)'. A unit test should be added at component level to verify the right processing of timeout, including this log trace.

Hide

Permalink

Christophe DENEUX added a comment - Mon, 4 Mar 2024 - 11:02:30 +0100

Added in trunk with svn#45199

Show

Christophe DENEUX added a comment - Mon, 4 Mar 2024 - 11:02:30 +0100 Added in trunk with svn#45199

Hide

Permalink

Christophe DENEUX added a comment - Mon, 4 Mar 2024 - 11:04:01 +0100

Reopened to be backported in branches 5.7.x and 5.8.x

Show

Christophe DENEUX added a comment - Mon, 4 Mar 2024 - 11:04:01 +0100 Reopened to be backported in branches 5.7.x and 5.8.x

Hide

Permalink

Christophe DENEUX added a comment - Mon, 4 Mar 2024 - 14:08:27 +0100

Backporterd in branch 5.7.x with svn#45204, svn#45207 and svn#45209

Show

Christophe DENEUX added a comment - Mon, 4 Mar 2024 - 14:08:27 +0100 Backporterd in branch 5.7.x with svn#45204, svn#45207 and svn#45209

Hide

Permalink

Christophe DENEUX added a comment - Fri, 8 Mar 2024 - 17:39:25 +0100

Backporterd in branch 5.8.x with svn#45232

Show

Christophe DENEUX added a comment - Fri, 8 Mar 2024 - 17:39:25 +0100 Backporterd in branch 5.8.x with svn#45232

Petals CDK

Add a log trace identifying clearly the invoked service operation initiating a timeout

Details

Issue Links

Activity

People

Dates