-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
clustering: Openfire admin console page 'conversations' can fail #120
Comments
Also reported by @annovanvliet at https://discourse.igniterealtime.org/t/classnotfoundexception-userparticipations-when-retrieving-active-conversations-in-a-cluster/ as well as by another community member at https://discourse.igniterealtime.org/t/cluster-problem/86031/ |
…on all cluster nodes separately.
- By default leave functionality as is. - Updated changelog.
…on all cluster nodes separately.
- By default leave functionality as is. - Updated changelog.
…on all cluster nodes separately.
- By default leave functionality as is. - Updated changelog.
This issue will be prevented by the fixes for igniterealtime/openfire-hazelcast-plugin#79, igniterealtime/openfire-hazelcast-plugin#81 and OF-2350. However, none of these will prevent a very similar issue that occurs when reloading or updating the plugin without an Openfire restart (the issue that is warned for with igniterealtime/openfire-hazelcast-plugin#74) |
… monitoring plugin objects that are exchanged with other cluster nodes in task execution
…ugin objects that are exchanged with other cluster nodes in task execution
…onversationEvent If ConversationEvent can't be marshalled to/from XML, then events won't ever be pushed successfully from junior cluster nodes to the senior node.
…n-specific The XmlSerializer was intended to be generic, but is used in only one invocation. To make it easier to test the implementation, this commit turns the generic implementation into something that is specific to this plugin.
Improved the XML-based serialization that got introduced as a fix for igniterealtime#120/igniterealtime#170 Dropped Externalization (supposed to be replaced with XML-based serialization) to reduce complexity. Added unit tests to verify XML-based serialization functionality.
…onversationEvent If ConversationEvent can't be marshalled to/from XML, then events won't ever be pushed successfully from junior cluster nodes to the senior node.
…n-specific The XmlSerializer was intended to be generic, but is used in only one invocation. To make it easier to test the implementation, this commit turns the generic implementation into something that is specific to this plugin.
Improved the XML-based serialization that got introduced as a fix for igniterealtime#120/igniterealtime#170 Dropped Externalization (supposed to be replaced with XML-based serialization) to reduce complexity. Added unit tests to verify XML-based serialization functionality.
…iterealtime#170 Adds igniterealtime#155 to the changelog. This issue was fixed as a side-effect of igniterealtime#120 and igniterealtime#170.
When the plugin is installed on all cluster nodes, and on a junior cluster node, the
Server > Archiving > Conversations
page is opened, then a blank page is shown and the following exceptions are logged.This problem does not occur on the senior cluster node.
This problem does not occur when there are no active conversations.
The text was updated successfully, but these errors were encountered: