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

Depends

Activity

Ascending order - Click to sort in descending order
Christophe DENEUX made changes - Wed, 28 Feb 2024 - 11:36:21 +0100
Field Original Value New Value
Link This issue depends on PETALSCDK-210 [ PETALSCDK-210 ]
Christophe DENEUX made changes - Wed, 28 Feb 2024 - 11:36:37 +0100
Link This issue blocks PETALSDISTRIB-587 [ PETALSDISTRIB-587 ]
Christophe DENEUX made changes - Wed, 28 Feb 2024 - 12:54:01 +0100
Summary The log trace identifying clearly the invoked service operation initiating a timeout is not generated The warning log trace identifying clearly the invoked service operation initiating a timeout is not generated
Priority Blocker [ 1 ]
Description The 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:
{code}
super.onExpiredAsyncJBIMessage(asyncExchange, asyncContext);
{code} 		The 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:
{code}
super.onExpiredAsyncJBIMessage(asyncExchange, asyncContext);
{code}
Christophe DENEUX made changes - Wed, 28 Feb 2024 - 17:42:32 +0100
Status New [ 10000 ] Open [ 10002 ]
Priority Blocker [ 1 ] Major [ 3 ]
Christophe DENEUX made changes - Wed, 28 Feb 2024 - 17:42:34 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Christophe DENEUX made changes - Thu, 29 Feb 2024 - 10:04:10 +0100
Summary The warning log trace identifying clearly the invoked service operation initiating a timeout is not generated A warning log trace identifying clearly the invoked service operation initiating a timeout is not generated
Description The 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:
{code}
super.onExpiredAsyncJBIMessage(asyncExchange, asyncContext);
{code} 		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:
{code}
super.onExpiredAsyncJBIMessage(asyncExchange, asyncContext);
{code}
Hide
Permalink
Christophe DENEUX added a comment - Tue, 5 Mar 2024 - 10:01:31 +0100

Fixed in master with git#816ffddd

Show
Christophe DENEUX added a comment - Tue, 5 Mar 2024 - 10:01:31 +0100 Fixed in master with git#816ffddd
Christophe DENEUX made changes - Tue, 5 Mar 2024 - 10:01:31 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 1.5.0 [ 11114 ]
Resolution Fixed [ 1 ]
Hide
Permalink
Christophe DENEUX added a comment - Tue, 5 Mar 2024 - 10:02:25 +0100

Reopened to backport in branches 1.3.x and 1.4.x

Show
Christophe DENEUX added a comment - Tue, 5 Mar 2024 - 10:02:25 +0100 Reopened to backport in branches 1.3.x and 1.4.x
Christophe DENEUX made changes - Tue, 5 Mar 2024 - 10:02:25 +0100
Status Resolved [ 10004 ] Open [ 10002 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Tue, 5 Mar 2024 - 10:02:26 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Hide
Permalink
Christophe DENEUX added a comment - Tue, 5 Mar 2024 - 11:43:00 +0100

Backported in branch 1.3.x with git#e5214feb

Show
Christophe DENEUX added a comment - Tue, 5 Mar 2024 - 11:43:00 +0100 Backported in branch 1.3.x with git#e5214feb
Christophe DENEUX made changes - Tue, 5 Mar 2024 - 11:43:08 +0100
Fix Version/s 1.3.3 [ 11200 ]
Affects Version/s 1.3.2 [ 11051 ]
Hide
Permalink
Christophe DENEUX added a comment - Fri, 15 Mar 2024 - 12:49:32 +0100

Backported in branch petals-se-flowable-1.4.x with git#5e90fcf9

Show
Christophe DENEUX added a comment - Fri, 15 Mar 2024 - 12:49:32 +0100 Backported in branch petals-se-flowable-1.4.x with git#5e90fcf9
Christophe DENEUX made changes - Fri, 15 Mar 2024 - 12:49:32 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 1.4.1 [ 11201 ]
Fix Version/s 1.5.0 [ 11114 ]
Resolution Fixed [ 1 ]
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
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.