Replace custom logging implementation with a third party library


Openfire has a proprietary implementation for its logging framework. We can improve and expand logging functionality by replacing that logging implementation with one of the many available libraries. Such implementations should be more flexible and more feature richt. An added benefit is that by doing so, we reduce the code in Openfire that we need to maintain, which will allow Openfire developers to focus better on what they're supposed to produce: code that relates to XMPP.




Guus der Kinderen
August 22, 2010, 6:32 AM

There is indeed some kind of problem in Kraken that relates to our new logging implementation (Kraken is already being translating several types of logging interfaces into each-other - this last translation appears to fail). I'll work with Daniel Henninger to resolve these. We'll do that outside the scope of though.

August 21, 2010, 5:10 PM

I have tested a few builds from Bamboo. Indeed 30 build has logs path fixed, but Kraken stopped working (Kraken is ok in Admin Console, but Spark doesnt see gateways). Builds 25, 26 are ok with Kraken. Build 27 throws a bunch of errors in launcher and doesn't work at all. 28 and 29 shows Wrong Parameter Usage error in launcher and server doesn't work.

Guus der Kinderen
August 21, 2010, 3:43 PM

I believe I have fixed this now. The install4j packager creates the Windows Launcher, which did not set the openfireHome variable. Wroot, could you verify the fix? You can download the new binary from (any build including or later than 30 will contain the fix).

Guus der Kinderen
July 29, 2010, 7:03 AM

grmbl. Reopening

July 29, 2010, 3:46 AM

Sorry, Guus. It's back. I have tried 3.7.0 beta.exe from here and when i run launcher it creates logs dir in C:\



Guus der Kinderen


Guus der Kinderen