Petals BC REST

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

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.3.0-BC , 2.4.0-BC
  • Fix Version/s: 2.3.3-BC , 2.4.1-BC
  • Component/s: Consumer mode
  • 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

Activity

Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
4s
1
Christophe DENEUX
Wed, 28 Feb 2024 - 13:18:06 +0100
Open Open In Progress In Progress
2s
1
Christophe DENEUX
Wed, 28 Feb 2024 - 13:18:08 +0100
In Progress In Progress Resolved Resolved
5d 4h 44m
1
Christophe DENEUX
Mon, 4 Mar 2024 - 18:02:27 +0100
Resolved Resolved Open Open
34s
1
Christophe DENEUX
Mon, 4 Mar 2024 - 18:03:01 +0100
Open Open In Progress In Progress
7d 20h 17m
1
Christophe DENEUX
Tue, 12 Mar 2024 - 14:20:04 +0100
In Progress In Progress Resolved Resolved
42s
1
Christophe DENEUX
Tue, 12 Mar 2024 - 14:20:46 +0100

People

Dates

  • Created:
    Wed, 28 Feb 2024 - 13:18:02 +0100
    Updated:
    Tue, 12 Mar 2024 - 14:20:46 +0100
    Resolved:
    Tue, 12 Mar 2024 - 14:20:46 +0100