GWWS Server Error Seen When Sending Soap Inbound Messages To Tuxedo Service

(Doc ID 1374673.1)

Last updated on JANUARY 19, 2018

Applies to:

Oracle Tuxedo - Version and later
Information in this document applies to any platform.
***Checked for relevance on 02-07-2013***


Customer gets failure on Soap input when trying to call Tuxedo service via SALT Inbound messaging.

With tracing turned on, you will see the following failure when parsing the input soap message:

GWWS.1208820.1034.0: TRACE:ms:SCO[4095] FSM State Transition:--None-->ParseSOAPBody
GWWS.1208820.1034.0: TRACE:ms:SCO[4095] FSM State Transition:--Default-->ParseBodyRoot
GWWS.1208820.1034.0: TRACE:ms:SCO[4095] FSM State Transition:--OK-->ParseBodyElement
GWWS.1208820.1034.0: TRACE:ms:Begin data transformation of request message, buffer type = FML32, SCO index=4095
GWWS.1208820.1034.0: TRACE:ms:SCO[4095] FSM State Transition:--Fail-->SOAPFault

Typically you will see one of two different types of soap envelope fault messages depending upon the input:

<SOAP-ENV:Envelope xmlns:SOAP-ENV="">
<faultstring>GWWS_CAT:1037: DataMapping Error: Tag 'urn:paramA' is unexpected.</faultstring>


<SOAP-ENV:Envelope xmlns:SOAP-ENV="">
<faultstring>GWWS_CAT:1060: Internal Error: Tuxedo application service don't return buffer with TPFAIL.</faultstring>


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