Petals BC Gateway

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: 1.1.0, 1.2.0
Fix Version/s: 1.1.1, 1.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 method 'onExpiredAsyncJBIMessage(...)' is not correctly inherited.

The call to the parent method is missing:

super.onExpiredAsyncJBIMessage(asyncExchange, asyncContext);
Show
A warning log trace identifying clearly the invoked service operation initiating a timeout is not generated because the method 'onExpiredAsyncJBIMessage(...)' is not correctly inherited. The call to the parent method is missing:

super.onExpiredAsyncJBIMessage(asyncExchange, asyncContext);

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:

Wed, 28 Feb 2024 - 13:13:53 +0100

Updated:

Tue, 12 Mar 2024 - 12:07:00 +0100

Resolved:

Tue, 12 Mar 2024 - 12:07:00 +0100