Petals BC Quartz

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.7.0, 1.8.0
  • Fix Version/s: 1.7.2, 1.8.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 service consumer send its messages using 'AbstractListener.send(...)' instead of using 'AbstractListener.sendAsync(...)',
    • and status replies are processed using 'AbstractJBIListener.onJBIMessage(...)' instead of using 'AbstractJBIListener.onAsyncJBIMessage(...)'.
    Show
    A warning log trace identifying clearly the invoked service operation initiating a timeout is not generated because:
    • the service consumer send its messages using 'AbstractListener.send(...)' instead of using 'AbstractListener.sendAsync(...)',
    • and status replies are processed using 'AbstractJBIListener.onJBIMessage(...)' instead of using 'AbstractJBIListener.onAsyncJBIMessage(...)'.
  • Environment:
    -

Issue Links

Activity

Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
24s
1
Christophe DENEUX
Thu, 29 Feb 2024 - 10:33:14 +0100
Open Open In Progress In Progress
1s
1
Christophe DENEUX
Thu, 29 Feb 2024 - 10:33:15 +0100
In Progress In Progress Resolved Resolved
4d 2h 58m
1
Christophe DENEUX
Mon, 4 Mar 2024 - 13:31:18 +0100
Resolved Resolved Open Open
32s
1
Christophe DENEUX
Mon, 4 Mar 2024 - 13:31:50 +0100
Open Open In Progress In Progress
1s
1
Christophe DENEUX
Mon, 4 Mar 2024 - 13:31:51 +0100
In Progress In Progress Resolved Resolved
7d 20h 18m
1
Christophe DENEUX
Tue, 12 Mar 2024 - 09:50:32 +0100

People

Dates

  • Created:
    Thu, 29 Feb 2024 - 10:32:50 +0100
    Updated:
    Tue, 12 Mar 2024 - 09:52:23 +0100
    Resolved:
    Tue, 12 Mar 2024 - 09:50:32 +0100