Petals BC MAIL

A warning log trace identifying clearly the invoked service operation initiating a timeout is not generated

View this issue in another formatViewView
- XML
- Word
- Printable

Details

Type: Bug
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: 4.1.0, 4.2.0
Fix Version/s: 4.1.1, 4.2.1
Component/s: None
Security Level: Public

Description:
Hide
A warning log trace identifying clearly the invoked service operation initiating a timeout is not generated because:

the service consumer send its messages using 'AbstractListener.send(...)' instead of using 'AbstractListener.sendAsync(...)',

and status replies are processed using 'AbstractJBIListener.onJBIMessage(...)' instead of using 'AbstractJBIListener.onAsyncJBIMessage(...)'.
Show
A warning log trace identifying clearly the invoked service operation initiating a timeout is not generated because:

the service consumer send its messages using 'AbstractListener.send(...)' instead of using 'AbstractListener.sendAsync(...)',

and status replies are processed using 'AbstractJBIListener.onJBIMessage(...)' instead of using 'AbstractJBIListener.onAsyncJBIMessage(...)'.

Environment:

-

Issue Links

Depends

This issue depends on:
~~PETALSCDK-210~~ Add a log trace identifying clearly the invoked service operation initiating a timeout

This issue blocks:
PETALSDISTRIB-587 Improve the identification of the service endpoint initiating a timeout

Activity

People

Assignee:

Christophe DENEUX

Reporter:

Christophe DENEUX
Watchers:

0

Dates

Created:

Thu, 29 Feb 2024 - 10:02:53 +0100

Updated:

Fri, 8 Mar 2024 - 18:18:52 +0100

Resolved:

Fri, 8 Mar 2024 - 18:18:52 +0100