RP/JOLT 1.2 - JRAD rejects a JRLY connection after a network outage. (Doc ID 769596.1)

Last updated on NOVEMBER 04, 2016

Applies to:

Oracle Tuxedo Jolt - Version 1.2 and later
Information in this document applies to any platform.
Information in this document applies to any platform
***Checked for relevance on 23-03-2011***


Goal

If a network connection between jrly and jrad is broken in Jolt 1.1, the jrly's first reconnection attempt fails.  Yet,
subsequent attempts succeed because the jrad gets notified of the network state, and closes the connection.  

However, in base Jolt 1.2, the jrad doesn't get notified of the broken network connection.  All attempts to reconnect
to jrad fail until the jrad is recycled.  

In the Jolt 1.2 rolling patch, the jrly cannot reconnect to jrad until the TCP keepalive timer expires.  When the TCP
keepalive timer expires, JRAD closes the network connection, and frees itself to accept a new jrly connection.  

A customer observed that a firewall timeout caused jrly to disconnect from jrad.  While this wasn't a problem in Jolt
1.1, it made his application unstable in Jolt 1.2.  The customer asked for the jrad in Jolt 1.2 to work like it did in
Jolt 1.1, which was more robust.

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