The Openfire FQDN is not unique to each host
Activity
Show:
Daryl Herzmann
changed the StatusSeptember 21, 2018 at 2:26 PMIn Progress
Resolved
Daryl Herzmann
updated the ResolutionSeptember 21, 2018 at 2:26 PMNone
Fixed
Greg Thomas
updated the Fix versionsAugust 26, 2018 at 3:40 PMNone
4.3.0
Greg Thomas
changed the StatusAugust 26, 2018 at 3:40 PMOpen
In Progress
Greg Thomas
changed the AssigneeAugust 26, 2018 at 3:40 PMDave Cridland
Greg Thomas
Greg Thomas
updated the Linked IssuesAugust 25, 2018 at 3:20 PMNone
This issue is related to OF-1259
Greg Thomas
updated the DescriptionJune 15, 2018 at 11:40 AMDuring setup, the user is prompted for a host-specific FQDN (as opposed to a cluster specific XMPP domain).
This FQDN is stored in the database in ofProperty as xmpp.fqdn - which means all nodes in a cluster receive the same FQDN, that of the last node in the cluster to go through the setup process.
Two things need to happen;
1) Store the FQDN in the openfire.xml file not the database, so it becomes host specific as it should be.
2) Check to see if where existing usage of the FQDN - whether it's retrieved directly using the "xmpp.fqdn" JiveGlobal, or indirectly via XMPPServerInfo.getHostname() - should be using the XMPP domain name (XMPPServerInfo.getXMPPDomain()) instead.
Note; at the very least [https://github.com/igniterealtime/Openfire/blob/master/src/java/org/jivesoftware/database/bugfix/OF1515.java#L118] is definitely the wrong usage.
During setup, the user is prompted for a host-specific FQDN (as opposed to a cluster specific XMPP domain).
This FQDN is stored in the database in ofProperty as xmpp.fqdn - which means all nodes in a cluster receive the same FQDN, that of the last node in the cluster to go through the setup process.
Two things need to happen;
1) Store the FQDN in the openfire.xml file not the database, so it becomes host specific as it should be.
2) Check to see if where existing usage of the FQDN - whether it's retrieved directly using the "xmpp.fqdn" JiveGlobal, or indirectly via XMPPServerInfo.getHostname() - should be using the XMPP domain name (XMPPServerInfo.getXMPPDomain()) instead.
Greg Thomas
created the IssueJune 15, 2018 at 11:39 AM
During setup, the user is prompted for a host-specific FQDN (as opposed to a cluster specific XMPP domain).
This FQDN is stored in the database in ofProperty as xmpp.fqdn - which means all nodes in a cluster receive the same FQDN, that of the last node in the cluster to go through the setup process.
Two things need to happen;
1) Store the FQDN in the openfire.xml file not the database, so it becomes host specific as it should be.
2) Check to see if where existing usage of the FQDN - whether it's retrieved directly using the "xmpp.fqdn" JiveGlobal, or indirectly via XMPPServerInfo.getHostname() - should be using the XMPP domain name (XMPPServerInfo.getXMPPDomain()) instead.