|
|
|
|
|
|
Call Descriptor Errors
Call descriptor errors occur as a result of exceeding the maximum limit of call descriptors or referencing an invalid value. Asynchronous and conversational calls return TPELIMIT when the maximum number of outstanding call descriptors has been exceeded. TPEBADDESC is returned when an invalid call descriptor value is specified for an operation.
Call descriptor errors occur only during asynchronous calls or conversational calls. (Call descriptors are not used for synchronous calls.) Asynchronous calls depend on call descriptors to associate replies with the corresponding requests. Conversational send and receive functions depend on call descriptors to identify the connection; the call that initiates the connection depends on the availability of a call descriptor.
Troubleshooting of call descriptor errors can be can be done by checking for specific errors at the application level.
Limit Errors
The system allows up to 50 outstanding call descriptors (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 call descriptors 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 call descriptor can become invalid and, if referenced, cause an error to be returned to tperrno(5) in either of two situations:
A call descriptor might become stale, for example, in the following circumstances:
|
|
|
|
|
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|