Petals CDK

No response to the service consumer if the message exchange is rejected by processors

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 5.1.3
  • Fix Version/s: 5.6.0
  • Component/s: runtime
  • Security Level: Public
  • Description:

    If no more message exchange processors is available or no thread is available to execute a message exchange processor, no response is sent to the service consumer. The service consumer will get a time-out as error, that is not the real error.

  • Environment:
    -

Issue Links

Depends

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Christophe DENEUX added a comment - Mon, 21 May 2012 - 16:10:25 +0200

Since PETALSCDK-91, a retry policy has been introduced at message exchange acceptor level. If no message exchange processor is available, a rety is done. But when the retry policy ends, the message exchange will be lost.
So to avoid to lose the message exchange, two ways exist:

  1. an error should be returned to the consumer,
  2. the acceptor thread could be used to run the message exchange processor, and so, the consumer will be indirectly slowed down.
    The better way is #2
Show
Christophe DENEUX added a comment - Mon, 21 May 2012 - 16:10:25 +0200 Since PETALSCDK-91, a retry policy has been introduced at message exchange acceptor level. If no message exchange processor is available, a rety is done. But when the retry policy ends, the message exchange will be lost. So to avoid to lose the message exchange, two ways exist:
  1. an error should be returned to the consumer,
  2. the acceptor thread could be used to run the message exchange processor, and so, the consumer will be indirectly slowed down. The better way is #2
Hide
Permalink
Christophe DENEUX added a comment - Thu, 31 May 2012 - 17:27:12 +0200

Delayed to 5.4.0

Show
Christophe DENEUX added a comment - Thu, 31 May 2012 - 17:27:12 +0200 Delayed to 5.4.0
Hide
Permalink
Victor NOËL added a comment - Fri, 19 Jun 2015 - 16:57:24 +0200

Once PETALSCDK-123 is fixed, we should introduce an alternative strategy (as stated in PETALSCDK-135) where after a certain (configurable) time, an error is set on the exchange with a petals-specific exception whose semantics is that there is no resource available to process the message.

Show
Victor NOËL added a comment - Fri, 19 Jun 2015 - 16:57:24 +0200 Once PETALSCDK-123 is fixed, we should introduce an alternative strategy (as stated in PETALSCDK-135) where after a certain (configurable) time, an error is set on the exchange with a petals-specific exception whose semantics is that there is no resource available to process the message.
Hide
Permalink
Victor NOËL added a comment - Thu, 29 Oct 2015 - 09:16:37 +0100

Reopened: it wasn't actually fixed, there was an error in bound checks and the message sending was never triggered when the max number of try was reached.

Show
Victor NOËL added a comment - Thu, 29 Oct 2015 - 09:16:37 +0100 Reopened: it wasn't actually fixed, there was an error in bound checks and the message sending was never triggered when the max number of try was reached.
Hide
Permalink
Victor NOËL added a comment - Thu, 29 Oct 2015 - 17:40:44 +0100

Resolved finally for 5.5.1

Show
Victor NOËL added a comment - Thu, 29 Oct 2015 - 17:40:44 +0100 Resolved finally for 5.5.1

People

Dates

  • Created:
    Thu, 5 Apr 2012 - 14:49:30 +0200
    Updated:
    Wed, 16 Dec 2015 - 16:27:47 +0100
    Resolved:
    Thu, 29 Oct 2015 - 17:40:44 +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.