History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JM-1300
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: Gaston Dombiak
Reporter: Gaston Dombiak
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Openfire

Room events should only be triggered in the node that generated the event

Created: 03/13/08 05:57 PM   Updated: 03/13/08 06:07 PM
Component/s: Core
Affects Version/s: 3.4.5
Fix Version/s: 3.5.0

Time Tracking:
Not Specified

Support Plan Customer Issue: No
Resolution Date: 03/13/08 06:07 PM
Acceptance Test - Add?: No


 Description  « Hide
Room events (e.g. room created, occupant joined, occupant left, etc.) should only be triggered in the node where the event took place. We are currently triggering it in each cluster node and that has two important consequences and one minor.

Important consequence:
1) Reduce MUC scalability since a lot more MUC events are flooding the cluster
2) Triggers cluster errors since it produces chain of events across cluster nodes using the coherence listener thread

Minor consequence:
1) Fills up logs with messages like: Found occupant that left the room but was not in the room



 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.