Petals ESB Container

No synchronization made by Petals container "master" node when restarted after crash (distributed configuration with at least 2 nodes)

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Critical Critical
  • Resolution: Won't Fix
  • Affects Version/s: 3.1
  • Fix Version/s: 5.0.0
  • Component/s: Registry
  • Security Level: Public
  • Description:
    Hide

    In Distributed configuration, when the master slave is stopped (expected situation or due to a crash) and restarted,
    unlike slave nodes which it synchronizes its "global registry state" knowledge before starting any of its local installed
    components/Service assembly, it does not. This means that if a component is installed in the master node and have to
    sends messages to endpoints located on some slave nodes that currently running then it will automatically failed because
    the message receiver endpoint is unknown.
    The problem can be reproduce with Logica use-case : petals-se-notification and petals-se-kpi component are supposed to be
    deployed one node - the "slave" one - whereas other components of the use-case are deployed on a different node

    • the "master" one. Then simulate crash on master node --> Notification producer can not send registerPublisher() request because
      the Notification broker endpoint is unknown.
    Show
    In Distributed configuration, when the master slave is stopped (expected situation or due to a crash) and restarted, unlike slave nodes which it synchronizes its "global registry state" knowledge before starting any of its local installed components/Service assembly, it does not. This means that if a component is installed in the master node and have to sends messages to endpoints located on some slave nodes that currently running then it will automatically failed because the message receiver endpoint is unknown. The problem can be reproduce with Logica use-case : petals-se-notification and petals-se-kpi component are supposed to be deployed one node - the "slave" one - whereas other components of the use-case are deployed on a different node
    • the "master" one. Then simulate crash on master node --> Notification producer can not send registerPublisher() request because the Notification broker endpoint is unknown.
  • Environment:
    Probably any. Tested on Linux OS

Activity

Ascending order - Click to sort in descending order
Roland Naudin made changes - Wed, 25 Aug 2010 - 15:21:33 +0200
Field Original Value New Value
Priority Critical [ 2 ]
Roland Naudin made changes - Wed, 25 Aug 2010 - 15:21:38 +0200
Status New [ 10000 ] Open [ 10002 ]
Christophe DENEUX made changes - Mon, 5 Oct 2015 - 11:50:06 +0200
Assignee Admin [ rnaudin ] Christophe DENEUX [ cdeneux ]
Christophe DENEUX made changes - Mon, 5 Oct 2015 - 11:50:10 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Hide
Permalink
Christophe DENEUX added a comment - Mon, 5 Oct 2015 - 11:50:34 +0200

As a new distributed registry, based on Hazelcast, has been introduced with Petals ESB 5.0.0, this issue will not be fixed.

Show
Christophe DENEUX added a comment - Mon, 5 Oct 2015 - 11:50:34 +0200 As a new distributed registry, based on Hazelcast, has been introduced with Petals ESB 5.0.0, this issue will not be fixed.
Christophe DENEUX made changes - Mon, 5 Oct 2015 - 11:50:34 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 5.0.0 [ 10413 ]
Resolution Won't Fix [ 2 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
9d 19h 15m
1
Roland Naudin
Wed, 25 Aug 2010 - 15:21:38 +0200
Open Open In Progress In Progress
1866d 20h 28m
1
Christophe DENEUX
Mon, 5 Oct 2015 - 11:50:10 +0200
In Progress In Progress Resolved Resolved
24s
1
Christophe DENEUX
Mon, 5 Oct 2015 - 11:50:34 +0200



People

Dates

  • Created:
    Sun, 15 Aug 2010 - 20:05:59 +0200
    Updated:
    Mon, 5 Oct 2015 - 11:50:34 +0200
    Resolved:
    Mon, 5 Oct 2015 - 11:50:34 +0200
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.