Table of Contents Previous Next PDF

Oracle Jolt Exceptions

Oracle Jolt Exceptions
This appendix describes all the Oracle Jolt exceptions that you may encounter. Keep in mind that the Jolt Class Library returns both Oracle Jolt and Oracle Tuxedo exceptions.
For details about Oracle Tuxedo exceptions, refer to the appropriate document in the following list:
The Jolt Class Library exceptions are listed for each class, constructor, and method listed in the Oracle Jolt API Reference.
The following table lists the Oracle Jolt and Oracle Tuxedo exceptions that you may encounter while running Oracle Jolt. Each exception includes a possible cause (or causes) and a recommended action (wherever possible) to help resolve the situation
A blocking condition has occurred and the TPNOBLOCK flag is specified in Oracle Tuxedo.
This exception occurs if a new JoltSession class is processed before performing the security protocol. In Jolt’s 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.
For 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.
A service routine has encountered an exception during tpreturn() or tpforward() in Oracle Tuxedo.
The 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.
A signal was received and the TPSIGSTRT flag was not specified.
For the JoltRemoteService class, the requested Oracle Tuxedo service does not recognize the type and subtype of the input data.
For the JoltRemoteService class, the Oracle Tuxedo caller does not recognize the type and the subtype of the reply data.
Usually, 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 Oracle Jolt that does not support the acknowledgment protocol.
The JoltUserEvent class has implemented a subscription to an asynchronous notification event, but the subscription has failed because it matches an existing subscription.
Usually, this exception occurs when an administrative request via tpadmcall() has failed in Oracle Tuxedo. However, TMIB calls are not available in Oracle Jolt.
The TPEJOLT exception could occur for any of the following reasons:
JoltSession class—the send(), recv() or cancel() methods throw TPEJOLT if the session object or message ID is invalid.
JoltSession class—throws TPEJOLT when TPINIT data conversion fails.
bea.jolt.pool.connection class—throws TPEJOLT when a run-time exception occurs.
JoltRemoteService—the call() method throws TPEJOLT when the buffer conversion between Oracle Jolt and Oracle Tuxedo fails, the requested service is not defined in the Jolt Repository, the requested service does not the right version, or the reply data conversion fails.
JoltUserEvent class—throws TPEJOLT when event name conversion fails, an invalid message ID is encountered, or unsolicited message data conversion fails.

Copyright © 1994, 2017, Oracle and/or its affiliates. All rights reserved.