1.2.6 What Happens if the Request Fails
The session pool distributes the requests equally among the sessions in the pool. It selects the least busy session to call the Tuxedo service. If the selected session is terminated before the Tuxedo service is called, the session pool redirects the service call to a different session, then establishes a new session to replace the disconnected one. The session pool uses a round-robin algorithm to select and establish a connection to a primary Jolt Server. If no primary Jolt Servers responds, the session pool connects to a failover server.
If no sessions are available from a session pool, or the session
pool is suspended, then a SessionPoolException
is
thrown.
Multiple requests can be grouped into a single transaction. When
a transaction fails, a TransactionException
is thrown.
This exception should be caught by the servlet and handled
appropriately. (Usually, the servlet performs a rollback.)
Parent topic: How Jolt for WebLogic Works