Petals SE Flowable

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: 1.3.2, 1.4.0
  • Fix Version/s: 1.3.3, 1.4.1
  • Component/s: Service engine
  • 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
6h 6m
1
Christophe DENEUX
Wed, 28 Feb 2024 - 17:42:32 +0100
Open Open In Progress In Progress
2s
1
Christophe DENEUX
Wed, 28 Feb 2024 - 17:42:34 +0100
In Progress In Progress Resolved Resolved
5d 16h 18m
1
Christophe DENEUX
Tue, 5 Mar 2024 - 10:01:31 +0100
Resolved Resolved Open Open
54s
1
Christophe DENEUX
Tue, 5 Mar 2024 - 10:02:25 +0100
Open Open In Progress In Progress
1s
1
Christophe DENEUX
Tue, 5 Mar 2024 - 10:02:26 +0100
In Progress In Progress Resolved Resolved
10d 2h 47m
1
Christophe DENEUX
Fri, 15 Mar 2024 - 12:49:32 +0100

People

Dates

  • Created:
    Wed, 28 Feb 2024 - 11:36:00 +0100
    Updated:
    Fri, 15 Mar 2024 - 12:49:32 +0100
    Resolved:
    Fri, 15 Mar 2024 - 12:49:32 +0100