-
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
Problem loading conversations in cluster #170
Comments
This is likely a duplicate of #120 |
Do you only see this error on the junior cluster node, or on both? |
Only on the junior node as far as I can see. At least this is shown only as part of a HazelcastSerializationException, which (looking at the code) can only occur when its a junior node executing a task on the cluster. (right?) |
Definitely feels like the same issue. |
Merged
guusdk
added a commit
to guusdk/openfire-monitoring-plugin
that referenced
this issue
Dec 21, 2021
…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.
guusdk
added a commit
to guusdk/openfire-monitoring-plugin
that referenced
this issue
Dec 22, 2021
…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.
guusdk
added a commit
to guusdk/openfire-monitoring-plugin
that referenced
this issue
Dec 22, 2021
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.
guusdk
added a commit
that referenced
this issue
Dec 23, 2021
guusdk
added a commit
that referenced
this issue
Dec 23, 2021
guusdk
added a commit
that referenced
this issue
Dec 23, 2021
mightymop
pushed a commit
to mightymop/openfire-monitoring-plugin
that referenced
this issue
Dec 23, 2021
…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.
mightymop
pushed a commit
to mightymop/openfire-monitoring-plugin
that referenced
this issue
Dec 23, 2021
…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.
mightymop
pushed a commit
to mightymop/openfire-monitoring-plugin
that referenced
this issue
Dec 23, 2021
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.
guusdk
added a commit
to guusdk/openfire-monitoring-plugin
that referenced
this issue
Jan 19, 2022
…iterealtime#170 Adds igniterealtime#155 to the changelog. This issue was fixed as a side-effect of igniterealtime#120 and igniterealtime#170.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While running Openfire 4.6.1 in a two-server cluster, the monitoring plugin 2.2.0 generated errors when using the search archive admin page. Some of the listed conversations showed no content, and 'null' for all fields.
In the openfire error log the following was seen:
The text was updated successfully, but these errors were encountered: