|
|
|
|
|
|
Communication Handle Errors
Communication handle errors occur as a result of exceeding the maximum limit of communication handles or referencing an invalid value. Asynchronous and conversational calls return TPELIMIT when the maximum number of outstanding communication handles has been exceeded. TPEBADDESC is returned when an invalid communication handle value is specified for an operation.
Communication handle errors occur only during asynchronous calls or conversational calls. (Call descriptors are not used for synchronous calls.) Asynchronous calls depend on communication handles to associate replies with the corresponding requests. Conversational send and receive routines depend on communication handles to identify the connection; the call that initiates the connection depends on the availability of a communication handle.
Communication handle errors can be done by checking for specific errors at the application level.
Limit Errors
The system allows up to 50 outstanding communication handles (replies) per context (or BEA Tuxedo application association). This limit is enforced by the system; it cannot be redefined by your application.
The limit for communication handles for simultaneous conversational connections is more flexible than the limit for replies. The application administrator defines the limit in the configuration file. When the application is not running, the administrator can modify the MAXCONV parameter in the RESOURCES section of the configuration file. When the application is running, the administrator can modify the MACHINES section dynamically. Refer to tmconfig, wtmconfig(1) in the BEA Tuxedo Command Reference for more information.
Invalid Descriptor Errors
A communication handle can become invalid and, if referenced, cause an error to be returned to TP-STATUS in either of two situations:
A communication handle might become stale, for example, in the following circumstances:
|
|
|
|
|
|
Copyright © 2001 BEA Systems, Inc. All rights reserved.
|