Job Queue Server License Priority
When multiple users request the same license, the RLM server grants it to the first user. Subsequent requests wait in a queue until the license becomes available. By default, this is handled on a first-come, first-served basis, so users requesting a license must wait until all previous requests have been fulfilled.
To prevent simulations on your Job Queue server from waiting for licenses due to other users blocking them, you can increase the priority of the license request from the machine running the Job Queue server. This option is only available when using GeoDict with a floating license.
To give higher priority to license requests from the machine running the Job Queue server, follow these steps:
Your GeoDict installation includes a file named m2m.opt, located at:
C:\Program Files\Math2Market GmbH\GeoDict 2026\RLM\m2m.opt
Copy this file to the directory on your RLM license server where the license files (*.lic) are stored.
Options (*.opt) files allow you to define rules for how licenses are allocated within your organization. For more details, refer to the Installation & Licensing user guide. The m2m.opt file contains entries like the following:
PRIORITY 1 geodictbase project GEODICT_JOBQUEUE
PRIORITY 1 geodict-processes project GEODICT_JOBQUEUE
PRIORITY 1 geodict-server project GEODICT_JOBQUEUE
PRIORITY 1 geodict-viewer project GEODICT_JOBQUEUE
PRIORITY 1 geodictcloud project GEODICT_JOBQUEUE
PRIORITY 1 fibergeo project GEODICT_JOBQUEUE
PRIORITY 1 fibergeo-processes project GEODICT_JOBQUEUE
These entries assign the highest PRIORITY of 1 to license requests associated with the project GEODICT_JOBQUEUE.
On the machine running the Job Queue server, define the following environment variable:
RLM_PROJECT=GEODICT_JOBQUEUE
This ensures that all license requests from this machine are tagged with the GEODICT_JOBQUEUE project.
Once configured, any queued license requests from the Job Queue server will be prioritized over requests from other machines, reducing delays for scheduled simulations.
For more information on priority handling in RLM, refer to the RLM documentation.