Idle conversation check

The Micro Focus Communications Server (MFCS) periodically tests idle conversations to ensure that they are still valid. A conversation is classified as "idle" if it is waiting for further processing by Enterprise Server, for example, because all Service Execution Processes (SEPs) are busy. If a conversation is waiting for data from the client, it is not idle but in receive state, where conversation closure or failure is normally determined quickly.

The tests performed by MFCS for idle conversations do not involve sending any data to the peer, and will not cause issues for any peer applications.

By default, tests are performed every 15 seconds. There are two types of tests:

• The error test checks to see if any error conditions have been posted for the conversation by the communications stack.
• The readability test checks to see if the conversation is readable, and if so, attempts to receive data from it.

Aspects of the idle conversation check can be customized. See [idle check] Section for more information.