Petals BC SOAP

Concurrency problems with the WS client pools and the placeholders reloading

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 4.4.0
  • Fix Version/s: 4.4.2
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    The problem is that when the placeholders are reloaded, the pools are destroyed, but problems can arise:

    • Some objects were not returned yet: they risk being returned to a newly created pool instead of the old one, or worst, an exception is thrown if there is not yet a new pool created (see PETALSBCSOAP-168).
    • The pool can be removed/closed after the pool is retrieved during a borrow, but before an object is actually borrowed from it and thus an exception is thrown by the pool because it is closed (see PETALSBCSOAP-171).
    • Maybe other problems... ?
    Show
    The problem is that when the placeholders are reloaded, the pools are destroyed, but problems can arise:
    • Some objects were not returned yet: they risk being returned to a newly created pool instead of the old one, or worst, an exception is thrown if there is not yet a new pool created (see PETALSBCSOAP-168).
    • The pool can be removed/closed after the pool is retrieved during a borrow, but before an object is actually borrowed from it and thus an exception is thrown by the pool because it is closed (see PETALSBCSOAP-171).
    • Maybe other problems... ?
  • Environment:
    -

Issue Links

Activity

People

Dates

  • Created:
    Fri, 30 Oct 2015 - 17:40:05 +0100
    Updated:
    Mon, 19 Sep 2016 - 14:52:49 +0200
    Resolved:
    Mon, 19 Sep 2016 - 14:52:49 +0200