RP/TUX 7.1 - JSH gives GPF when concurrent Jolt clients request from Haleakala after 30 iter - CR040830
(Doc ID 767168.1)
Last updated on JANUARY 19, 2018
Applies to:Oracle Tuxedo / Tuxedo / 7,1
Information in this document applies to any platform
DESCRIPTION: JSH gives GPF when multiple Jolt client tries to access Tuxedo server from Haleakala after some time (it is working fine upto 30 itearion of each client). Following is the test scenario 1. Call TOUPPER service & SLEEP service from Jolt client in infinite loop. 2. SLEEP service just sleep for 120 seconds & TOUPPER returns string If we don't call SLEEP service it works fine. JSL configuration in ubbconfig file is JSL SRVGRP=JSL_GRP SRVID=2 CLOPT= " -- -n //MALAR:27000 -d /dev/tcp -m2 -M4 -x10" Jolt Connection Pool configuration in config.xml file of Haleakala is <JoltConnectionPool MaximumPoolSize="1" MinimumPoolSize="1" Name="joltpool" PrimaryAddresses="//22.214.171.124:27000" RecvTimeout="0" SecurityContextEnabled="false" Targets="myserver" /> ULOG file in server side gives the following error message after JSH gives GPF 102349.MALAR!JSH.208.86.-2: JOLT_CAT:1518: ERROR: Call handle and clientid have no matching requests This happens with Haleakala load 10 as Jolt Client and Tuxedo 7.1 as server, where server was running in Windows NT. Note :- 1. It happens only while running multiple Jolt clients concurrently from Haleakala. 2. Single Jolt client from Haleakala which runs continuously works fine (ran same client continuously for 18 hours) This problem can be reproducable by running concurrent clients in a infinite loop. - S.Malar Raj email@example.com Extn : 3378
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document