Petals SE POJO

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.6.0, 2.7.0
  • Fix Version/s: 2.6.1, 2.7.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

Activity

Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
5s
1
Christophe DENEUX
Thu, 29 Feb 2024 - 15:34:44 +0100
Open Open In Progress In Progress
1s
1
Christophe DENEUX
Thu, 29 Feb 2024 - 15:34:45 +0100
In Progress In Progress Resolved Resolved
4d 17h 48m
1
Christophe DENEUX
Tue, 5 Mar 2024 - 09:23:23 +0100
Resolved Resolved Open Open
47s
1
Christophe DENEUX
Tue, 5 Mar 2024 - 09:24:10 +0100
Open Open In Progress In Progress
1s
1
Christophe DENEUX
Tue, 5 Mar 2024 - 09:24:11 +0100
In Progress In Progress Resolved Resolved
8d 1h 55m
1
Christophe DENEUX
Wed, 13 Mar 2024 - 11:19:23 +0100

People

Dates

  • Created:
    Thu, 29 Feb 2024 - 15:34:39 +0100
    Updated:
    Wed, 13 Mar 2024 - 11:19:30 +0100
    Resolved:
    Wed, 13 Mar 2024 - 11:19:23 +0100