RP/Tux 8.1 - RP 109 > JSH session detruction prior to Idle Timeout (Doc ID 775549.1)

Last updated on NOVEMBER 04, 2016

Applies to:

Oracle Tuxedo / Tuxedo / 8.1
Information in this document applies to any platform

Goal

Customer Problem:
This problem should be very easy to reproduce.  You create a domain with the JSL configured with a -T (idle timeout)
value of 1 minute.  You set the services handled by the domain to have a large service timeout, let's say 10 minutes
in this case.  You create a service that runs until just before the service timeout, I just put a sleep in there to
emulate this.  

You now connect your Jolt Client to the server where the connection is made in RETAINED mode.  I do this using a IDLE
TIMEOUT of 1.  You then invoke the long running service. After ~3 minutes it times out.  Customer believes that this
behaviour is contrary to what is expected because the JSL should not timeout because the client connection is
non-idle.

Steps to recreate problem:
Setup JSL with -T 1 
Put sleep of about 5 minutes in simpserv
Run Jolt client to call toupper.
After about 2 - 3 minutes the client is terminated with reason that it was idle.

I suggested to customer that the JSL does not have a chance to know 
Reproduction environment is Tuxedo 8.1 with RP 114. 
Customer would like this fixed across all platforms.

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