Message Class 0003 - EntireX ACI - Conversation Ended

The conversation cannot be found, or no request is available for processing. This response is returned when:

1. The wrong conversation ID is specified.

2. A server issued a non-blocked RECEIVE with CONV-ID=NEW/ANY and no conversation or request is available for processing.

3. Neither the client nor the server has accessed the conversation for the specified timeout period. The conversation is timed out and does not exist anymore (if a conversation timeout occurs while users are waiting, they are informed with error code 0073). For the Broker, timeout is specified by the CONV-NONACT parameter in the attribute file.

Situation 1 is a user error. Check the program and correct the error.

For situation 2, contact the administrator and check the value supplied for CONV-NONACT. It may have to be increased. However, be sure not to supply too high a value as this can lead to resources being used for a long period of time.

For situation 3, this is an information-type message. How the program continues depends on the application.

The partner has ended of the conversation by either an EOC or DEREGISTER with OPTION=IMMED. This response is returned when:

1. The user has retrieved all the data/messages sent by the partner with RECEIVE calls and has attempted to get further data/message with a RECEIVE using the OPTION=NEXT. No more messages are available from the partner.

2. A function other than RECEIVE is issued and the partner has already ended the conversation.

This is an informational message. How the program continues depends on the application. Messages from the partner not yet received can be received with subsequent RECEIVE calls, that is, when the conversation end is detected by a call other than RECEIVE, it is possible that messages from the partner exist.

This error comes as the result of a receive function. The particular conversation is already closed because the partner application has DEREGISTERed. This information is intended to tell an application the reason for an EOC:
DEREGISTER of the partner,
LOGOFF of the partner, or
EOC with cancel of the partner

If possible, back out all actions taken for that conversation, since the end does not appear to be graceful.

The partner marked the conversation as cancelled with the EOC operation.

If possible, back out all actions taken for the conversation.

This error results from an attempted receive on a conversation that is already closed because the partner application performed a LOGOFF.

If possible, back out all actions taken for the conversation.

The partner for the conversation is no longer active. All conversations with this partner are terminated. This occurs when the partner has not issued a call to EntireX Broker for the time defined by either CLIENT-NONACT or SERVER-NONACT. Error code 0002 is returned to the partner when it attempts to access any of its previous conversations.

If this happens repeatedly, contact the administrator and check the value supplied for CLIENT-NONACT or SERVER-NONACT. It may need to be increased. However, do not supply too high a value, as this can lead to resources being used for a long period of time.

The timeout defined for the conversation has elapsed without the partner issuing a Broker call against the conversation and therefore the conversation has ended. For the Broker, timeout is specified by the CONV-NONACT value for the service in the attribute file.

Check the following causes:

• Ensure that the partner is working correctly.

• Contact the administrator and check the settings of the non-activity timeout. You may need to increase the timeout value. Do not supply too high a value, however, as this can lead to resources being used for a long period of time.