We're updating the issue view to help you get more done. 

Disabling clustering never completes

Description

Steps to reproduce;

  1. Install a fresh Openfire, enable hazelcast clustering.

  2. Login to Openfire, navigate to the "Clustering" page. Select "Disabled", and click "Save Settings".

Expected results

  • The Clustering page indicates that clustering is disabled.

Actual results

  • The browser shows a NullPointerException from Openfire. The server stops responding. It is necessary to stop and restart Openfire, at which point the Clustering page indicates that clustering is disabled.

Environment

None

Activity

Show:
Greg Thomas
March 1, 2018, 3:30 PM

Initial analysis;

After the node leaves the cluster, CacheFactory.leftCluster() is called - this attempts to copy all the data out of the clustered caches back in to the default caches.

But, because Hazelcast is shutdown, as soon as an attempt is made to read the clustered data an exception is thrown leaving the whole server (and probably every server in the ex-cluster) in a rather dodgy state.

Greg Thomas
March 1, 2018, 4:33 PM

NB. Fixed, but requires HZ-9 to be effective, and that is a fix to core Openfire itself.

Fixed

Assignee

Greg Thomas

Reporter

Greg Thomas

Labels

None

Ignite Forum URL

None

Fix versions

Priority

Major
Configure