Petals CDK

[Notification] Notification Publishers not unregistered on componant "stop" when the se-notification service is unavailable

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 5.0.3
  • Fix Version/s: 5.1.1
  • Component/s: Notifications
  • Security Level: Public
  • Description:
    Hide

    Usecase :

    • 1 petals instance with se-notification and se-kpi
    • 1 petals instance with components producing notifications
    • First, stop petals instance containing se-notif
    • Then, stop petals instance containing notification producers (components with notification property = "true")

    Producer never be unregistered. You could see that the "work/SavePublisherRegistrationRPs" directory of se-notif component contains publisher registrations.
    When you restart petals instances, an incoherant situation is obtained where notifications are duplicated because the same producer is registered twice.

    Show
    Usecase :
    • 1 petals instance with se-notification and se-kpi
    • 1 petals instance with components producing notifications
    • First, stop petals instance containing se-notif
    • Then, stop petals instance containing notification producers (components with notification property = "true")
    Producer never be unregistered. You could see that the "work/SavePublisherRegistrationRPs" directory of se-notif component contains publisher registrations. When you restart petals instances, an incoherant situation is obtained where notifications are duplicated because the same producer is registered twice.
  • Environment:
    petals-esb 3.1.x, petals-se-notif 1.0.x, petals-se-kpi 1.1.x, petals-cdk 5.0.x

Issue Links

People

Dates

  • Created:
    Tue, 21 Sep 2010 - 17:34:27 +0200
    Updated:
    Tue, 23 Nov 2010 - 15:38:40 +0100
    Resolved:
    Wed, 13 Oct 2010 - 14:26:45 +0200