Here is exactly what I do to bump it up. This is a direct copy and paste from another thread on this topic which is mentioned below. I see no reason why this wouldn’t work on OSX client.
Here’s what you need to do:
System Preferences > OpenFire > Stop Server (It’s important the server stops this way, cleanly)
Open terminal, sudo -s into root
Ok, now look for
under that add this:
You can set those settings to whatever you’d like, now save the file (ctrl+x > y)
This is where things get tricky, on Windows/Unix, you’re done, you just restart the server and it’s good to go.
I’m not sure if this was a mistake, or intentional, however it doesn’t look like OpenFire actually uses /usr/local/openfire/bin/openfire.sh to start, instead it uses this file: nano /usr/local/openfire/bin/extra/openfire-launchd-wrapper.sh
That’s where the problem truly is, you need to edit that file:
/usr/bin/java -server -jar “$OPENFIRE_HOME/lib/startup.jar” -Dopenfire.lib.dir=/usr/local/openfire/lib&
And replace it with:
/usr/bin/java -server -jar $OPENFIRE_OPTS “$OPENFIRE_HOME/lib/startup.jar” -Dopenfire.lib.dir=/usr/local/openfire/lib&
I think this might be a bug in OpenFire that the folks at Ignite should take a look at.
Either way, save that (ctrl + x > y), go back to System Preferences > OpenFire, and start the server.
You should now be good to go!
Referenced from this link…