RP/TUX 8.0 - JOLT 8.0 - Blocking Timeout Exception Thrown Even Though RecvTimeout Parameter Set

(Doc ID 775747.1)

Last updated on NOVEMBER 04, 2016

Applies to:

Oracle Tuxedo Jolt
Information in this document applies to any platform.
Information in this document applies to any platform

Goal

DESCRIPTION:
JOLT connection pools are used from within WLS 8.1 to communicate with Tuxedo 8.0. Even though the RecvTimeout
parameter associated with the JOLT connection pool is set to a very large number, the JOLT client is still subject to
blocking timeouts. It is desired that the client be immune to blocking timeouts (similar in functionality to
bea.jolt.JoltRequest.setNoTimeOut parameter)

CONFIGURATION:
Tuxedo 8.0

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms