Request limit (throttling)

Availability of functionality depends on the license and may not be available in all deployments.

Limit of active request instances

Limit of active request instances (so-called throttle) allows you to limit the number of simultaneously running requests of a given type on a specific server. After the limit is exceeded, the user cannot start another instance – instead, an information page is displayed.

This solution is especially useful in situations of increased system load or during maintenance work.

Configuration

The configuration of limits is done in the file:

/etc/eximee/webforms.xml

Changes in the file are applied without the need to restart the Tomcat server.

Sample configuration in the .xml file:

<webforms>
    <server> 
        <limits>
            <forms>
                <_uwmappertest>3</_uwmappertest>
                <_demo_porownywarka_ofert>3</_demo_porownywarka_ofert>
            </forms>
        </limits>
    </server>
</webforms>

In the tag <forms> we define the requests covered by the limit:

<_FORMNAME>LIMIT</_FORMNAME>

Where:

• FORMNAME – request name,
• LIMIT – maximum number of active instances.

Important rules:

• each request name FORMNAME must have the _ prefix
• no entry means no limit,
• setting the value to 0 means complete blocking of the request.

Configuration examples

Complete blocking of the request

<_przykladowy_wniosek>0</_przykladowy_wniosek>

After opening the request, the user will see a page informing them that it is unavailable.

Limiting the number of instances

<_przykladowy_wniosek>2</_przykladowy_wniosek>

A third attempt to start the request will result in an error page being displayed.

Information page

The text on the information page can be set from Eximee Designer, in the Library → Content and by searching for formatted content error_page_formLimitExceeded.

You also need to update the file webforms-error-pages.xml by adding the fragment below:

<code_formLimitExceeded>
    <content>error_page_formLimitExceeded-*</content>
</code_formLimitExceeded>