Openfire (ARCHIVED)

ComponentEventListener is not working correctly when running in a cluster

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 3.5.0
  • Fix Version/s: 3.6.0
  • Component/s: Core
  • Labels:
    None
  • Acceptance Test - Add?:
    No

Description

ComponentEventListener is currently being used like this:
. A registered event is triggered every time a new connection of an existing component connects
. Events are not clustered. That means that only the JVM where the component connected will get the event
. An unregistered event is triggered only in the JVM and when the last connection of a component was closed
. API is passing a Component object that is never used (and implies more work if we want to make it cluster ready)

Instead is should be like this:
. A registered event should be triggered only once and only when the component connected for the first time in that JVM and in the cluster
. The registered event should be broadcast to the other cluster nodes
. Change the API to only send the address of the component and not the component itself
. An unregistered event should be triggered when the service of the component is no longer available in the cluster

Activity

There are no comments yet on this issue.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: