Advanced users may wish to pass in parameters to the Java virtual machine (VM) to customize the runtime environment of Openfire. You can do this by creating vmoptions files in the bin/ directory of your Openfire installation. For the Windows service, you’d create a new text file called openfire-service.vmoptions. Each parameter to the VM should be on a new line of the file. For example, to set the minimum heap size to 512 MB and max VM heap size to 1024 MB, you’d use:
-Xms512m
-Xmx1024m
Sample file for Openfire running as a windows service attached.
You must leave the file as attached other than the actual content. Do not change the extension. For openfire you may want to read your install docs located in your Openfire directory. The install documentation should tell you how to do it for your system.
Also that file is specifically for users running openfire as a windows service. If you manually have to start openfire after logging into windows you need to rename the file as it says in the instructions included here:
To create parameters for the normal launcher, create a file called openfired.vmoptions (since the openfire.exe launcher invokes the openfired.exe executable to actually start the server).
Works fine to me, im using wildfire 3.1.1 running as service. Just put the openfire-service.vmoptions in bin folder, restarted the service and now my wildfire process are using near 250mb of memory. Before this procedure, wildfire uses no more than 128mb, causing some crashes when have mare than 200 users online.
I’ll monitor the server for some days to see if crashes stop.
I have some doubts:
how can wildfire works with this openfire-service.vmoptions file? dont need to be something like wildfire-service.vmoptions?
ill upgrade to openfire 3.4.5 in some days (or weeks), will this file work in openfire version ?