Message Class 0037 - EntireX ACI - Broker Resource Shortage

All resources reserved for that particular service are already in use. No additional resources can be assigned.

Wait a while and try again - the resource shortage may have been resolved. If this happens frequently for a particular service, the assigned resources are not sufficient. Add additional resources (conversations) to this service.

All resources reserved for that particular service are already in use. No additional resources can be assigned.

Wait a while and try again - the resource shortage may have been resolved. If this happens frequently, for a particular service, the assigned resources are not sufficient. Add additional resources (short or long buffers) to this service.

This is a resource shortage. Currently, no short message containers are available. Short message containers are used for data/messages shorter than or equal to 2048 bytes.

Because this is a temporary resource shortage, it makes sense to try the SEND call later in hope that the resource shortage is over. Be careful not to have a loop programmed in this situation. If this occurs frequently, increase the number of short message containers defined in the section DEFAULTS=BROKER with the keyword NUM-SHORT-BUFFER.

This is a resource shortage. Currently, no long message containers are available. Long message containers are used for data/messages longer than 2048 bytes.

Because this is a temporary resource shortage, it makes sense to try the SEND call later in hope that the resource shortage is over. Be careful not to have a loop programmed in this situation. If this occurs frequently, increase the number of long message containers defined in the section DEFAULTS=BROKER with the keyword NUM-LONG-BUFFER.

EntireX Broker detected an error while searching for a free TOQ entry. There is no TOQ entry for usage.

Contact Software AG support.

The timeout manager is currently using the participant control block to do a cleanup. Therefore, the resource is temporarily locked.

Retry the call to EntireX Broker.

This situation occurs only when working with the TOKEN parameter in the API; that is, the user is identified by USER-ID/TOKEN instead of USER-ID/Internal ID. If the user changes the physical location between EntireX Broker calls (e.g. a new session from another terminal), and a call to EntireX Broker from the old session is in progress, the new session retrieves this response. The new session is not accepted.

Retry the call to EntireX Broker later. To avoid confusion, however, do not have several concurrent sessions with the same TOKEN parameter in the API.

This is a temporary resource shortage. The maximum number of EntireX Broker conversations that can be active at any one time has been reached. New conversations will not be accepted until existing ones are ended by EOC calls or timeouts.

Increase NUM-CONVERSATION in the Broker attribute file or check that the timeout settings for CONV-NONACT for the services are not too high.

A request was issued while another request was already actively being processed for the same USER-ID/TOKEN combination.

Ensure that there are not two or more active applications specifying the same USER-ID/TOKEN value.

The attempt to create a service control block with the same identification at the same time is rejected. Since this is a very short time window, it is unlikely to get the error response.

Retry the call to EntireX Broker. If this occurs frequently, contact Software AG support.

The attempt to create a participant control block with the same identification at the same time is rejected. Since this is a very short time window, it is unlikely to get the error response.

Ensure that there are not two or more active applications specifying the same USER-ID/TOKEN value.

Broker serializes any request to create a new topic. The topic with the supplied topic name is currently created.

Retry the call to EntireX Broker.

This is a temporary resource shortage. The maximum number of EntireX Broker publications that can be active at any one time has been reached. New publications will not be accepted until existing ones are acknowledged by all subscribers.

Increase NUM-PUBLICATION in the Broker attribute file.

This is a resource shortage. Currently, new publications are not allowed. This situation can occur when the Broker administrator has issued the CIS command FORBID-NEWUOWMSGS to disallow new UOW and publication messages or the Broker was started with the NEW-UOW-MESSAGES=NO.

Since this is a resource shortage, it may be take some time before new publication messages are allowed again by the Broker administrator. Be careful not to have a loop programmed in this situation. Retry the call to EntireX Broker later after the Broker administrator has issued the command ALLOW-NEWUOWMSGS to allow new UOW and publication messages.

This is a resource shortage. Currently, new UOW messages are not allowed. This situation can occur when the Broker administrator has issued the CIS command FORBID-NEWUOWMSGS to disallow new UOW messages or the Broker was started with attribute NEW-UOW-MESSAGES=NO. See FORBID-NEWUOWMSGS under Broker CIS Data Structures and NEW-UOW-MESSAGES=NO under Broker Attributes.

Since this is a resource shortage, it may be take some time before new UOW messages are allowed again by the Broker administrator. Be careful not to have a loop programmed in this situation. Retry the call to EntireX Broker later after the Broker administrator has issued the CIS command ALLOW-NEWUOWMSGS to allow new UOW messages. See ALLOW-NEWUOWMSGS.

All servers reserved for that particular service are already in use. No additional servers can be assigned.

Wait a while and try again; the resource shortage may have been resolved. If this happens frequently for a particular service, the assigned resources are not sufficient. Add additional resources (servers) to this service.

The maximum number of 32 RECEIVE-PUBLICATION sessions per subscriber and topic is reached.

Commit received publications before starting to receive other new publications of that particular topic.

All resources reserved for that particular topic are already in use. No additional resources can be assigned.

Wait a while and try again - the resource shortage may have been resolved. If this happens frequently, for a particular topic, the assigned resources are not sufficient. Add additional resources (short or long buffers) to this topic.

All resources reserved for that particular topic are already in use. No additional resources can be assigned.

Wait a while and try again - the resource shortage may have been resolved. If this happens frequently, for a particular topic, the assigned resources are not sufficient. Add additional resources (publications) to this topic.

The internal heap is exceeded.

Increase the HEAP-SIZE and restart Broker.

Existing memory pool is full. Dynamic pool management is not enabled.

Request is rejected due to insufficient resources.

The number of slots for the memory pool exceeds the address space limit.

Change the attribute value. Contact Software AG support if you are not sure about the responsible attribute.

The requested slot size exceeds the total capacity of the memory pool. The request is rejected due to insufficient resources. This error usually occurs if a broker message exceeds the size of the long messge buffer.

Define an appropriate size for the memory pool to handle such a large buffer. Make sure that
NUM-LONG is at least MAX-MESSAGE-LENGTH / 4096, and
NUM-COMBUF is at least MAX-MESSAGE-LENGTH / 16384.

The allocation of this pool will exceed MAX-MEMORY and is rejected.

Increase value of Broker-specific attribute MAX-MEMORY, or no action if maximum value was defined correctly. See MAX-MEMORY under Broker Attributes.