Petals BC SOAP

Refactor ws client pool configuration and probes

Details

  • Type: Improvement Request Improvement Request
  • Status: New New
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: 5.0.0
  • Fix Version/s: None
  • Component/s: Monitoring (Technical)
  • Security Level: Public
  • Description:

    To be confirmed: as is, wsClientPoolExhaustions should always be 0 because another exhaustions should happen before at MessageExchangeProcessors level.

    Instead it would be interesting to be able to configure different ws-client pools.

  • Environment:
    -

Activity

Pierre Souquet made changes - Tue, 20 Nov 2018 - 10:58:04 +0100
Field Original Value New Value
Assignee Christophe DENEUX [ cdeneux ]
Priority Minor [ 4 ]
Christophe DENEUX made changes - Thu, 22 Nov 2018 - 09:27:41 +0100
Description To be confirmed: as is, {{wsClientPoolExhaustions}} should always be 0 because exhaustions should happen at {{MessageExchangeProcessors}} level.

Instead it would be interesting to be able to configure different ws-client pools.
To be confirmed: as is, {{wsClientPoolExhaustions}} should always be 0 because another exhaustions should happen before at {{MessageExchangeProcessors}} level.

Instead it would be interesting to be able to configure different ws-client pools.



People

Dates

  • Created:
    Tue, 20 Nov 2018 - 10:57:24 +0100
    Updated:
    Thu, 22 Nov 2018 - 09:27:41 +0100