Autosetup should not force the default database connection provider when using default auth provider

Description

When using ‘autosetup’, this snippet from XMPPServer.java ensures that when the default authprovider mode is used, the database connection provider will always be the default provider. This prevents the usage of another database connection provider, such as the one used for the embedded database.

The effect of this is code is that when configured to use the embedded database, Openfire will typically start up initially (in which it will use the embedded database), but will fail to restart without an error (as it cannot connect to an SQL database).

Environment

None

Activity

Show:

Guus der Kinderen June 29, 2023 at 8:45 AM

As a work-around for this problem, modify openfire.xml after you’ve stopped Openfire, and restore this fragment:

Openfire should then start up properly again.

Fixed

Details

Assignee

Reporter

Fix versions

Priority

Created March 27, 2023 at 12:42 PM
Updated July 20, 2023 at 8:51 PM
Resolved July 20, 2023 at 8:43 PM