PluginManager shouldn't attempt to load a plugin forever


Currently, Openfire's PluginManager will attempt to load a plugin over and over again in the case of a failure with loading the plugin. In the scenario of an administrator that does not have filesystem access to Openfire, this presents a problem as there is no mechanism to stop this process, to at least stop the logs from reporting the same error over and over again. Some suggestions regarding this for consideration.

  1. PluginManager should eventually 'give up' loading a plugin after so many failures.

  2. Openfire console should allow removal of uploaded jar files that did not properly load, so to stop the loading process

Just wanted to file a ticket to start a discussion on this issue.




Daryl Herzmann
January 4, 2019, 4:39 PM

I don't believe this to be an issue anymore.

Guus der Kinderen
November 13, 2017, 8:30 PM

I can still reproduce this (by chown'ing /openfire/plugins to root, and copy in a new plugin - it won't be allowed to extract, over and over and over and over again).

Daryl Herzmann
November 13, 2017, 3:38 PM

Guus did a bunch of work on plugin loading and I don't think this is anymore valid. Have assigned to him for his commentary.

Your pinned fields
Click on the next to a field label to start pinning.


Guus der Kinderen


Daryl Herzmann