Projects tigase _server server-core Issues #597
Issue with EventBus in cluster (#597)
Andrzej Wójcik (Tigase) opened 10 years ago
Due Date
2015-11-11

When using EventBusComponent in cluster mode there are a few issues:

  • component needs to be manually added (I think it should be added and started when we use Tigase XMPP Server in cluster mode)

  • component do not add component JID on other cluster nodes to affiliations so events from other cluster nodes are lost (dropped with error forbidden).

  • Andrzej Wójcik (Tigase) commented 10 years ago

    I already implemented automatic addition of JIDs of EventBusComponent from other cluster nodes to affiliations with owner affiliation.

    %wojtek - what do you think about adding EventBusComponent to list of always active components? (active by default)

  • Wojciech Kapcia (Tigase) commented 10 years ago

    Andrzej Wójcik wrote:

    %wojtek - what do you think about adding EventBusComponent to list of always active components? (active by default)

    I think it's a good idea - I was under the impression (based on previous discussions) it was already included as one of the default components.

  • Andrzej Wójcik (Tigase) commented 10 years ago

    I added EventBusComponent to list of components started by default

  • Wojciech Kapcia (Tigase) commented 10 years ago

    With the latest fix from Bartek eventbus now works correctly and doesn't fall into infinite loop in cluster. I also works correctly while being loaded by default.

  • Artur Hefczyc commented 10 years ago

    Why is this changed back to QA?

  • Wojciech Kapcia (Tigase) commented 10 years ago

    Because it turned out there is still some problems with duplicating events in cluster.

  • Wojciech Kapcia (Tigase) commented 10 years ago

    commit:0c185d26f9aaab580fb79a6bf6dde67d2868f72d resolved the issue, hopefully for good this time.

issue 1 of 1
Type
Bug
Priority
Normal
Assignee
RedmineID
3688
Version
tigase-server-7.1.0
Spent time
0
Issue Votes (0)
Watchers (0)
Reference
tigase/_server/server-core#597
Please wait...
Page is in error, reload to recover