GWWS is Getting High CPU when there is Namespace issue in SOAP Header

(Doc ID 2316570.1)

Last updated on OCTOBER 11, 2017

Applies to:

Oracle Service Architecture Leveraging Tuxedo (SALT) - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

On Tuxedo SALT 12.1.3 version, when upgraded the patch from RP05 to RP013, GWWS is getting high CPU when payload  SOAP header is having incorrect namespace.

ERROR
-----------------------
In Server side top indicate GWWS CPU increase to 100%
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
14971 tux 20 0 460m 24m 10m S 100.3 0.3 22:37.19 GWWS

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. Build and run SALT sample simpapp server available in $TUXDIR/samples/salt/simpapp
2.Modify the simpclient.c to add SOAP Header like customer's provided below.
$TUXDIR/samples/salt/simpapp/simpclient/simpclient.c

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header>
<a:Action s:mustUnderstand="1">rvS101HKPTiedot</a:Action>
<a:MessageID>urn:uuid:7c842eb8-55c2-4d2b-8488-7767430b91f0</a:MessageID>
<a:ReplyTo
125034.tapastest.idc.oracle.com!GWWS.14971.2662516480.0: TRACE:ws:>
<a:Address>http://www.w3.org/2005/08/addressing/anonymous</a:Address>
</a:ReplyTo>
<a:To s:mustUnderstand="1">http://soke-saltgw1.temo.fi:10020/URA</a:To>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<ns1:ToUpperWS xmlns:ns1="urn:pack.simpapp_typedef.salt11">
<ns1:inbuf>abc</ns1:inbuf>
</ns1:ToUpperWS>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

3. Build and run the client:
./simpclient <GWWS Host> <GWWS port> abc -v

4. In Server side top indicate GWWS CPU increase to 100%
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
14971 tux 20 0 460m 24m 10m S 100.3 0.3 22:37.19 GWWS

5. If GWWS trace is enable in ULOG below entry is seen and then there is no
more entry:
export TMTRACE=msg:ulog
export GWWS_TRACE_LEVEL=100

125034.tapastest.idc.oracle.com!GWWS.14971.2662516480.0: TRACE:ws:parse_header_field() return 6
125034.tapastest.idc.oracle.com!GWWS.14971.2662516480.0: TRACE:ws:SCO[4095] FSM State Transition: --OK-->HTTPDispatch
125034.tapastest.idc.oracle.com!GWWS.14971.2662516480.0: TRACE:ws:GWWS_CAT:1628: TRACE: A HTTP message is received, SCO index=4095
125034.tapastest.idc.oracle.com!GWWS.14971.2662516480.0: TRACE:ws:Finding endpoint, soap->path is /simpapp, request_uri is /simpapp
125034.tapastest.idc.oracle.com!GWWS.14971.2662516480.0: TRACE:ws:SCO[4095] FSM State Transition: --Post-->ParseSOAPHeader
125034.tapastest.idc.oracle.com!GWWS.14971.2662516480.0: TRACE:ws:SCO[4095] FSM State Transition: --Default-->ParseHeaderRoot
125034.tapastest.idc.oracle.com!GWWS.14971.2662516480.0: TRACE:ws:GWWS_CAT:1612: TRACE: A SOAP message is received, SCO index=4095
125034.tapastest.idc.oracle.com!GWWS.14971.2662516480.0: TRACE:ws:SCO[4095] FSM State Transition: --OK-->ParseHeaderElement

 

Changes

 

Cause

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