Message Class 0037 - EntireX ACI - Broker Resource Shortage

This message class is returned when resources to satisfy the EntireX Broker operation are temporarily unavailable The resource for which the shortage occurred must be determined by examining the error number returned. This situation is also reported in the Broker's log data set. However, no conversations are lost. On the client side, after a reasonable time, the Broker function can be retried. Ensure that no loop has been programmed. The messages have the format:

0037nnnn

where 0037 is the message class, and
nnnn is the message number in the range 0000 - 9999

Overview of Messages

00370041 | 00370042 | 00370057 | 00370061 | 00370099 | 00370165 | 00370197 | 00370230 | 00370364 | 00370365 | 00370366 | 00370367 | 00370390 | 00370417 | 00370445 | 00370448 | 00370484 | 00370486 | 00370489 | 00370620 | 00370656 | 00370669 | 00370670 | 00370671

00370041 CONV-LIMIT for service reached
Explanation

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

Action

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.


00370042 BUFFER-LIMIT for service reached
Explanation

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

Action

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.


00370057 ATTR: Shortage For NUM-SHORT-BUFFERS
Explanation

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.

Action

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.


00370061 ATTR: Shortage For NUM-LONG-BUFFER
Explanation

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

Action

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.


00370099 No free timeout queue entry
Explanation

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

Action

Contact Software AG support.


00370165 Participant locked by Timeout manager
Explanation

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

Action

Retry the call to EntireX Broker.


00370197 Reconnect Rejected - User Busy
Explanation

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.

Action

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.


00370230 Max NUM-CONVERSATION Reached
Explanation

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.

Action

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


00370364 Participant Already Active
Explanation

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

Action

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


00370365 Service Currently Created
Explanation

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.

Action

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


00370366 Participant Currently Created
Explanation

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.

Action

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


00370367 Topic currently created
Explanation

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

Action

Retry the call to EntireX Broker.


00370390 Max NUM-PUBLICATION reached
Explanation

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.

Action

Increase NUM-PUBLICATION in the Broker attribute file.


00370417 PSI: New publications are not allowed
Explanation

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.

Action

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.


00370445 PSI: New UOW messages are not allowed
Explanation

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.

Action

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.


00370448 SERVER-LIMIT for Service reached
Explanation

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

Action

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.


00370484 All subscription sessions in use
Explanation

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

Action

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


00370486 BUFFER-LIMIT for Topic reached
Explanation

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

Action

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.


00370489 PUBLICATION-LIMIT for Topic reached
Explanation

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

Action

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.


00370620 Heap overflow
Explanation

The internal heap is exceeded.

Action

Increase the HEAP-SIZE and restart Broker.


00370656 Dynamic pool management not enabled
Explanation

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

Action

Request is rejected due to insufficient resources.


00370669 Allocation size is out of range
Explanation

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

Action

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


00370670 Slot size is greater than entire pool
Explanation

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.

Action

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.


00370671 Requested allocation exceeds MAX-MEMORY
Explanation

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

Action

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