Compatibilidad :2.2.7
Ediciones :Edición ProfesionaEdición EstándarEdición de la Comunidad
Plataformas :WindowsMac OSX (No Soportado)Linux (No Soportado)IBM AIX (No Soportado)FreeBSD (No Soportado)HP-UX (No Soportado)Solaris (No Soportado)IBM z/OS (No Soportado)IBM z/Linux (No Soportado)


DO NOT modify the value of this property while an application using the configuration file has been installed as a Windows Service. Please uninstall the existing service BEFORE modifying this property. The service with the new value can then be safely reinstalled later.

This property is only used on Windows platforms.

Specifies the priority at which the Wrapper and its JVM will be run at when run as a Windows Service or as a console application.

Possible values are:

  • LOW,
  • BELOW_NORMAL, (Note: Not supported on Windows NT, 95 or 98)
  • ABOVE_NORMAL, (Note: Not supported on Windows NT, 95 or 98)
  • HIGH,

The default value is NORMAL.



Changing this property to HIGH or REALTIME makes the Wrapper and its JVM consume all available CPU first. It will only yield CPU to other processes when it does not need the cycles itself. This will cause a number of problems including an unresponsive UI (User Interface).

We have seen problems with timeouts, between the Wrapper and its JVM, when the JVM is outputting large quantities of console output and consuming CPU 100%, for long periods of time. If you change this default value and if you are experiencing such timeouts, please return the property to the default NORMAL priority before contacting our support.


Changes to the value of this property will not have any affect on the priority of the Wrapper process if the configuration is reloaded. Any restarted JVM will take on the newly configured priority however. The Wrapper must be restarted for changes to take effect on the Wrapper process.


From the Windows API, each priority level is described as follows:


Specify this level for a process with no special scheduling needs.


Specify this level for a process whose threads run only when the system is idle. The threads of the process are preempted by the threads of any process running in a higher priority level. An example is a screen saver. The idle-priority "LOW" level is inherited by child processes.


Specify this level for a process that performs time-critical tasks that must be executed immediately. The threads of the process preempt the threads of "NORMAL" or "LOW" level processes. An example is the Task List,which must respond quickly when called by the user, regardless of the load on the operating system. Use extreme care when using the high-priority level, because a high-priority level application can use nearly all available CPU time.


Specify this level for a process that has the highest possible priority. The threads of the process preempt the threads of all other processes, including OS (operating system) processes performing important tasks. For example, a real-time process that executes for more than a very brief interval can cause disk caches not to flush or cause the mouse to be unresponsive.