TUEXDO错误说明

1. TPEABORTA transaction could not commit.CauseThis exception occurs because a transaction could not commit on the server side. This exception may also occur if the JSH performs a message resend for a commit that has timed out due to a previous blocking condition. In BEA Tuxedo, you can get this exception if tpcommit() is called with outstanding replies or open conversation connections.ActionCheck transaction failures on the server side. BEA Jolt clients should resend the request after the transaction problem has been fixed on the server side.2. TPEBADDESCThis exception should not occur in BEA Jolt.CauseIn BEA Tuxedo, this exception usually occurs when an invalid caller descriptor is given to tpgetrply() or tpsend().ActionNone.3. TPEBLOCKA blocking condition has occurred and theTPNOBLOCK flag is specified in BEA Tuxedo.Cause This exception occurs because the server is backed up.ActionYou may need to re-examine and re-architect the application to handle extreme load cases.4. TPEINVALInvalid arguments were given by the application.CauseThis exception occurs if a new JoltSession class is processed before performing the security protocol. In Jolts URL handler routine, this exception occurs when a invalid challenge response is received by the openConnection() method. The TPEINVAL exception can also occur if you specified a hexadecimal address for the JSL -H option without a leading 0x , or if you entered a wrong address in UBBCONFIG file. In addition, the GETREC(), DELREC() and GETSVC() services in JREPSVR can return TPEINVAL if the REPNAME is missing. Also, the ADDREC() service in JREPSVR can return TPEINVAL if the REPVAL is not specified.ActionThis type of exception should have been handled during the application development cycle. You should not receive this exception in a production environment.5. TPELIMITThe maximum number of outstanding requests or subscriptions has been reached.Cause The maximum number of outstanding requests has been reached. This exception could also mean that the BEA Tuxedo System Event Brokers maximum number of subscriptions (50 internally defined for now) has been reached.ActionYou may need to re-examine and re-architect the application to handle load extreme cases.6. TPENOENTThe requested service is not available.CauseUsually, the requested service is not booted or advertised on the BEA Tuxedo server side. It is also possible that the requested service is not defined in the Jolt Repository. This exception could also indicate that you could not access the BEA Tuxedo System Event Broker.ActionYou need to check the server side to see if the service is booted or advertised. Otherwise, check to see if the requested service is defined in the Jolt Repository. After the service is available on the server side, Jolt clients should resend the request.7. TPEOSAn operating system exception has occurred.CauseThe exact nature of the problem is described in the ULOG file. Typically, you can get this exception due to the memory allocation failures, wrong network address, or failure to attach to the Bulletin Board for the JSL.ActionTry fixing the problem as described in the ULOG file. Jolt clients might need to reconnect or resend the request after the problem has been fixed.8. TPEPERMThere is a permission problem when attempting to join a session.CauseIn the JoltSession class, this exception occurs because the Jolt client does not have the permission to join the application. Permission may be denied based on an invalid application password, failure to pass application specific authentication, or the use of restricted client names. In the Jolt URL handler routing, this exception occurs when a bad challenge response is received on the openConnection() method. If the Jolt Repository is set to read-only, the ADDREC() and DELREC() services, or the GARBAGECOLLECT() service in JREPSVR, also return the TPEPERM exception.ActionThis type of exception should have been handled during the application development cycle. You should not receive this exception in a production environment.9. TPEPROTOA function was called in an improper context.CauseFor this exception, an improper context could include a rollback() or commit() method called by a participant, an unsubscribe event that is called while unsubscribe all is in progress, or when the caller is not a client.ActionThis type of exception should have been handled during the application development cycle. You should not receive this exception in a production environment.10. TPESVCERRA service routine has encountered an exception duringtpreturn() ortpforward() in BEA Tuxedo.CauseThe service routine is returning application-level failures, which may include any of the following: an application calls tpreturn() or tpforward() with invalid flags, the caller descriptor is no longer valid, or there are invalid return values.ActionThis type of exception should have been handled during the application development cycle. You should not receive this exception in a production environment.11. TPESVCFAIL The service routine sending the callers reply calledtpreturn() withTPFAIL.Cause The service routine is returning application-level failures.ActionThis type of exception should have been handled during the application development cycle. You should not receive this exception in a production environment.12. TPESYSTEMA BEA Tuxedo system exception has occurred.CauseThe exact nature of the exception is written to the ULOG file. For example, when performing the Diffie-Hellman encryption, this exception occurs if the JSH is unable to send negotiation parameters. The JSL fails to send the reply challenge call to the Jolt client. The Jolt client sends an incorrect timestamp value, an incorrect number of encrypted bits value, an incorrect ticket value, or timestamp mismatches in reconnect protocol. The JSL fails to initialize network protocol information, or could not establish a listening address on a network. The JSH receives a network message with an unknown context or receives a message with a different connection.ActionIn most cases, you need to find out the exact nature of the exception from the ULOG file on the server side. In case of hardware or network failures, you can try to reconnect if a hardware or network failover is available.13. TPETIMEA transaction timeout has occurred.Cause There is a transaction timeout on the server side.ActionThis type of exception should be addressed on the application server side. Jolt clients should resend the request after the server side problem has been resolved.14.TPETRANThe requested service belongs to a server that does not support transactions andTPNOTRAN is not set.Cause A transaction is not supported for the requested service.ActionThis type of exception should be addressed on the application server side. Jolt clients should resend the request after the server side problem has been resolved.15. TPGOTSIGAn unexpected signal was received.Cause A signal was received and the TPSIGSTRT flag was not specified.ActionNone.16.TPERMERRA resource manager failed to open or close correctly on the server side.CauseThe resource manager might not be available; or all the resource might not be released or committed before close.ActionCheck the ULOG file for reasons why the resource manager failed to open or close on the server side.17.TPEITYPEFor theJoltRemoteService class, the requested BEA Tuxedo service does not recognize the type and subtype of the input data.Cause The type and subtype of input data is not defined in the Jolt Repository.ActionThe type and subtype of input data should be defined in the Jolt Repository. This type of exception should have been handled during the application development cycle. You should not receive this exception in a production environment.18. TPEOTYPEFor theJoltRemoteService class, the BEA Tuxedo caller does not recognize the type and the subtype of the reply data.Cause The type and subtype of output data is not defined in the Jolt Repository.ActionThe type and subtype of output data should be defined in the Jolt Repository. This type of exception should have been handled during the application development cycle. You should not receive this exception in a production environment.19. TPERELEASEThis exception should not occur in BEA Jolt.CauseUsually, this exception occurs when an unsolicited notification message is sent from a server with the TPACK flag set, and the target is a Jolt client from an older release of BEA Jolt that does not support the acknowledgment protocol.ActionVerify that the correct version of BEA Jolt is installed on your machine. This type of exception should have been handled during the application development cycle. You should not receive this exception in an production environment.20. TPEHAZARDDue to some failure, the work done on behalf of the transaction may have been heuristically completed.Cause Check the ULOG file on the server side for details.ActionNone.21. TPEHEURISTICDue to a heuristic decision, the work done on behalf of the transaction was partially committed and partially aborted.Cause Check the ULOG file on the server side for details.ActionNone.22.TPEEVENTThis exception should not occur in BEA Jolt.CauseUsually, this exception means that an event has occurred when sending or receiving a message in a conversational connection in BEA Tuxedo. However, conversational server connections are not available in BEA Jolt.ActionNone.23. TPEMATCHTheJoltUserEvent class has implemented a subscription to an asynchronous notification event, but the subscription has failed because it matches an existing subscription.CauseThe subscription failed because it matched one already listed with the BEA Tuxedo System Event Broker.ActionNone.24.TPEDIAGNOSTIC This exception should not occur in BEA Jolt.CauseUsually, this exception occurs when enqueuing or dequeuing a message from the specified queue fails in BEA Tuxedo. However, enqueing and dequeing of messages is not available in BEA Jolt.ActionNone.25. TPEMIBThis exception should not occur in BEA Jolt.Cause Usually, this excepti