why the tuxedo-service can't receive mesage through GWWS of SALT - Service Architecture Leveraging Tuxedo (SALT)

My app using SALT can't receive information from GWWS .
the client is soapUI 3.0.1,it sends webservice request message to tuxedo using SALT,the tracelog seems GWWS has receive request successful,but my tuxedo-serivce receive nothing;but my app send webserivce response to soapUI client successful,the soapUI client receives response info ok too.
the tracelog is :
153834.tydic36!GWWS.160526.1034.0: TRACE:ms:SCO[4095] FSM State Transition: WAKEUP>Created
153834.tydic36!GWWS.160526.1034.0: TRACE:ms:SCO[4095] FSM State Transition: Inbound>Receive
153834.tydic36!GWWS.160526.1034.0: TRACE:ms:SCO[4095] FSM State Transition: WAKEUP>Receive
153834.tydic36!GWWS.160526.1034.0: TRACE:ms:SCO[4095] FSM State Transition: Found>ParseHTTP
153834.tydic36!GWWS.160526.1034.0: TRACE:ms:HTTP Parsing: Buffer length 500 -- POST /simpapp HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: text/xml;charset=UTF-8
SOAPAction: "ToUpperWS"
User-Agent: Jakarta Commons-HttpClient/3.1
Host: 192.168.161.36:8088
Content-Length: 288
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:pack.simpapp_typedef.salt11">
<soapenv:Header/>
<soapenv:Body>
<urn:ToUpperWS>
+<urn:inbuf>HELLO</urn:inbuf>(here the gwws reveive message ok )+ </urn:ToUpperWS>
<
153834.tydic36!GWWS.160526.1034.0: TRACE:ms:/soapenv:Body>
</soapenv:Envelope>
153834.tydic36!GWWS.160526.1034.0: TRACE:ms:parse_header_field() return 6
153834.tydic36!GWWS.160526.1034.0: TRACE:ms:SCO[4095] FSM State Transition: OK>HTTPDispatch
153834.tydic36!GWWS.160526.1034.0: TRACE:ms:A HTTP message is received, SCO index=4095
153834.tydic36!GWWS.160526.1034.0: TRACE:ms:Finding endpoint, soap->path is /simpapp, request_uri is /simpapp
153834.tydic36!GWWS.160526.1034.0: TRACE:ms:SCO[4095] FSM State Transition: Post>ParseSOAPHeader
153834.tydic36!GWWS.160526.1034.0: TRACE:ms:SCO[4095] FSM State Transition: Default>ParseHeaderRoot
153834.tydic36!GWWS.160526.1034.0: TRACE:ms:A SOAP message is received, SCO index=4095
153834.tydic36!GWWS.160526.1034.0: TRACE:ms:SCO[4095] FSM State Transition: None>ParseSOAPBody
153834.tydic36!GWWS.160526.1034.0: TRACE:ms:SCO[4095] FSM State Transition: Default>ParseBodyRoot
153834.tydic36!GWWS.160526.1034.0: TRACE:ms:SCO[4095] FSM State Transition: OK>ParseBodyElement
153834.tydic36!GWWS.160526.1034.0: TRACE:ms:Begin data transformation of request message, buffer type = STRING, SCO index=4095
153834.tydic36!GWWS.160526.1034.0: TRACE:ms:SCO[4095] FSM State Transition: OK>WSSEPolicyCheck1
153834.tydic36!GWWS.160526.1034.0: TRACE:ms:SCO[4095] FSM State Transition: OK>WSRMHandle1
153834.tydic36!GWWS.160526.1034.0: TRACE:ms:SCO[4095] FSM State Transition: OK>FindService
153834.tydic36!GWWS.160526.1034.0: TRACE:ms:SCO[4095] FSM State Transition: OK>XML2Tux
153834.tydic36!GWWS.160526.1034.0: TRACE:ms:SCO[4095] FSM State Transition: OK>CallTuxService
153834.tydic36!GWWS.160526.1034.0: TRACE:ms:SCO[4095] FSM State Transition: Default>SendInput
153834.tydic36!GWWS.160526.1.0: TRACE:ms:Delivering a message to Tuxedo, service name =TOUPPER, SCO index=4095
+153834.tydic36!testmgr.221608.1.0: rqst->data[][0]+(here the tux-service recevies nothing)
the app:
TOUPPER(rqst)
TPSVCINFO *rqst;
#endif
{
int i;
     userlog("rqst->data[%s][%d]",rqst->data,rqst->len);
for( i=0; i<rqst->len-1; i++ )
{
rqst->data[i] = toupper(rqst->data);
}
char SndBuf = tpalloc("STRING", NULL, 16);  /申请发送的缓存*/
if (SndBuf == NULL)
{
          userlog("err");      
          tpreturn( TPSUCCESS, 0, rqst->data, 0L, 0 );
}
     SndBuf[0] = 'H';
     SndBuf[1] = 'O';
     SndBuf[2] = 0;
/* Return the transformed buffer to the requestor. */
tpreturn( TPSUCCESS, 0, SndBuf, 0L, 0 );
}
Edited by: user13389469 on 2010-8-11 上午12:58
Edited by: user13389469 on 2010-8-11 上午12:58 

the soap client send message:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:pack.simpapp_typedef.salt11">
<soapenv:Header/>
<soapenv:Body>
<urn:ToUpperWS>
<urn:inbuf>HELLO</urn:inbuf>
</urn:ToUpperWS>
</soapenv:Body>
</soapenv:Envelope>
and receive message is ok:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tuxedo="urn:pack.simpapp_typedef.salt11">
<SOAP-ENV:Body>
<tuxedo:ToUpperWSResponse>
<tuxedo:outbuf>HO</tuxedo:outbuf>
</tuxedo:ToUpperWSResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
my question is that,why my app receive nothing by "userlog("rqst->data[%s][%d]",rqst->data,rqst->len);"; but send back ok "<tuxedo:outbuf>HO</tuxedo:outbuf>"?
the metadata is that:
service=ToUpperWS
servicetype=service
inbuf=STRING
outbuf=STRING
tuxservice=TOUPPER
param=name
type=string
access=inout
size=100
Edited by: user13389469 on 2010-8-11 上午1:14 

I have resolve it ,I build the testmgr using tuxedo8.1,and the envirement is tuxedo11,so the error comes.

Related

GWWS_CAT:1022: SOAP Error: Invalid SOAP Body While processing Valid Soap Request

Hi, I Following tuxedo version on AIX 6.1 Power 7 64 bit.INFO: Oracle Tuxedo, Version 10.3.0.0, 64-bit, Patch Level 095 Service Meta Information is :service=StockQuoteexport=yservicetype=servicetuxservice=STOCKQUOTEsvcdescription=This service is used to demo security and xml buffer interop.inbuf=XMLoutbuf=XMLparam=XMLBuffertype=xmlaccess=inoutsize=1000 this is actually picked from salt sample packaged with version 10.3. Request Message:<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns1="urn:salt.samples.wsdl" xmlns:ns2="urn:pack.samples_typedef.salt11"><SOAP-ENV:Body><ns2:StockQuote><ns2:inbuf></ns2:inbuf></ns2:StockQuote></SOAP-ENV:Body></SOAP-ENV:Envelope> I put GWWS under tracing and found following. Response Messag:150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --WAKEUP-->Created150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --Inbound-->Receive150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --Found-->ParseHTTP150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:HTTP Parsing: Buffer length 1140 -- POST /secsapp HTTP/1.1^MHost: uaix4070.unix.rabobank.nl:8070^MUser-Agent: gSOAP/2.7^MContent-Type: text/xml; charset=utf-8^MContent-Length: 437^MConnection: close^MSOAPAction: "StockQuote"^M^M<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLS150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:chema" xmlns:ns1="urn:salt.samples.wsdl" xmlns:ns2="urn:pack.samples_typedef.salt11"><SOAP-ENV:Body><ns2:StockQuote><ns2:inbuf></ns2:inbuf></ns2:StockQuote></SOAP-ENV:Body></SOAP-ENV:Envelope>  150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:parse_header_field() return 6150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->HTTPDispatch150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:A HTTP message is received, SCO index=4095150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:Finding endpoint, soap->path is /secsapp, request_uri is /secsapp150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --Post-->ParseSOAPHeader150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --Default-->ParseHeaderRoot150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:A SOAP message is received, SCO index=4095150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --None-->ParseSOAPBody150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --Default-->ParseBodyRoot150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->ParseBodyElement150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:Begin data transformation of request message, buffer type = XML, SCO index=4095150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --Fail-->SOAPFault150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->PackSOAPBody150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->PackSOAPHeader150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --Default-->WSRMHandle3150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->PackHTTP150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --Default-->Send150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:Sending HTTP Header: HTTP/1.1 500 Internal Server Error^MServer: gSOAP/2.7^MContent-Type: text/xml; charset=utf-8^MContent-Length: 311^MConnection: close^M^M  150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:Sending SOAP Message: <?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode>SOAP-ENV:Client</faultcode><faultstring>GWWS_CAT:1022: SOAP Error: Invalid SOAP Body.</faultstring></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope> Is there something wrong with the request ? Are there known bugs with handling of Soap request in this version ? Thanks & Regards,Ajeet Tewari
Ajeet, I believe that may be caused by the fact that the payload is empty (<inbuf></inbuf>). The gateway is very strict on that... Regards, Maurice

Problem running datatypeapp example for SALT 10gR3

Hello,
After getting help here in Problem running simpapp example for SALT 10gR3 I am also asking for some tips in second example.
I obtain "org.apache.axis2.AxisFault: GWWS_CAT:1034: DataMapping Error: Failed to parse tag 'tf32flat'." from Axis Client.
Below I enclose HTTP streams as well as trace from ULOG from GWWS service.
Any help will be very apprciated.
regards Olek
==============
Listen Port: 6666
Target Host: L375
Target Port: 7777
==== Request ====
POST /TuxAll HTTP/1.1
Content-Type: text/xml; charset=UTF-8
SOAPAction: "QUERY"
User-Agent: Axis2
Host: L375:6666
Transfer-Encoding: chunked
1c7
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><ns1:QUERY xmlns:ns1="urn:pack.TuxAll_typedef.salt11"><inbuf><ns1:tf32char>5</ns1:tf32char><ns1:tf32shrt>7</ns1:tf32shrt><ns1:tf32flat>1.1</ns1:tf32flat><ns1:tf32v32><ns1:tv32char>67</ns1:tv32char><ns1:tv32shrt>6</ns1:tv32shrt><ns1:tv32flat>2.2</ns1:tv32flat></ns1:tf32v32></inbuf></ns1:QUERY></soapenv:Body></soapenv:Envelope>
0
==== Response ====
HTTP/1.1 500 Internal Server Error
Server: gSOAP/2.7
Content-Type: text/xml; charset=UTF-8
Content-Length: 398
Connection: close
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAP-ENV:Fault><faultcode>SOAP-ENV:Client</faultcode><faultstring>GWWS_CAT:1034: DataMapping Error: Failed to parse tag 'tf32flat'.</faultstring></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
==============
ULOG :
192217.L375!GWWS.5732.4408.0: GWWS_CAT:19: INFO: GWWS started.
192225.L375!GWWS.5732.5112.0: TRACE:ms:SCO[4095] FSM State Transition: WAKEUP>Created
192225.L375!GWWS.5732.5112.0: TRACE:ms:SCO[4095] FSM State Transition: Inbound>Receive
192225.L375!GWWS.5732.5112.0: TRACE:ms:SCO[4095] FSM State Transition: Found>ParseHTTP
192225.L375!GWWS.5732.5112.0: TRACE:ms:HTTP Parsing: Buffer length 119 -- POST /TuxAll HTTP/1.1
Content-Type: text/xml; charset=UTF-8
SOAPAction: "QUERY"
User-Agent: Axis2
Host: L375:6666
192225.L375!GWWS.5732.5112.0: TRACE:ms:parse_header_field() return 4
192225.L375!GWWS.5732.5112.0: TRACE:ms:SCO[4095] FSM State Transition: NotFound>Receive
192225.L375!GWWS.5732.5112.0: TRACE:ms:SCO[4095] FSM State Transition: Found>ParseHTTP
192225.L375!GWWS.5732.5112.0: TRACE:ms:HTTP Parsing: Buffer length 497 -- Transfer-Encoding: chunked
1c7
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><ns1:QUERY xmlns:ns1="urn:pack.TuxAll_typedef.salt11"><inbuf><ns1:tf32char>5</ns1:tf32char><ns1:tf32shrt>7</ns1:tf32shrt><ns1:tf32flat>1.1</ns1:tf32flat><ns1:tf32v32><ns1:tv32char>67</ns1:tv32char><ns1:tv32shrt>6</ns1:tv32shrt><ns1:tv32flat>2.2</ns1:tv32flat></ns1:tf32v32></inbuf></ns1:QUERY></soapenv
192225.L375!GWWS.5732.5112.0: TRACE:ms::Body></soapenv:Envelope>
0
192225.L375!GWWS.5732.5112.0: TRACE:ms:parse_header_field() return 1
192225.L375!GWWS.5732.5112.0: TRACE:ms:SCO[4095] FSM State Transition: OK>HTTPDispatch
192225.L375!GWWS.5732.5112.0: TRACE:ms:A HTTP message is received, SCO index=4095
192225.L375!GWWS.5732.5112.0: TRACE:ms:Finding endpoint, soap->path is /TuxAll, request_uri is /TuxAll
192225.L375!GWWS.5732.5112.0: TRACE:ms:SCO[4095] FSM State Transition: Post>ParseSOAPHeader
192225.L375!GWWS.5732.5112.0: TRACE:ms:SCO[4095] FSM State Transition: Default>ParseHeaderRoot
192225.L375!GWWS.5732.5112.0: TRACE:ms:A SOAP message is received, SCO index=4095
192225.L375!GWWS.5732.5112.0: TRACE:ms:SCO[4095] FSM State Transition: None>ParseSOAPBody
192225.L375!GWWS.5732.5112.0: TRACE:ms:SCO[4095] FSM State Transition: Default>ParseBodyRoot
192225.L375!GWWS.5732.5112.0: TRACE:ms:SCO[4095] FSM State Transition: OK>ParseBodyElement
192225.L375!GWWS.5732.5112.0: TRACE:ms:Begin data transformation of request message, buffer type = FML32, SCO index=4095
192225.L375!GWWS.5732.5112.0: TRACE:ms:SCO[4095] FSM State Transition: OK>WSSEPolicyCheck1
192225.L375!GWWS.5732.5112.0: TRACE:ms:SCO[4095] FSM State Transition: OK>WSRMHandle1
192225.L375!GWWS.5732.5112.0: TRACE:ms:SCO[4095] FSM State Transition: OK>FindService
192225.L375!GWWS.5732.5112.0: TRACE:ms:SCO[4095] FSM State Transition: OK>XML2Tux
192225.L375!GWWS.5732.5112.0: TRACE:ms:SCO[4095] FSM State Transition: Fail>SOAPFault
192225.L375!GWWS.5732.5112.0: TRACE:ms:SCO[4095] FSM State Transition: OK>PackSOAPBody
192225.L375!GWWS.5732.5112.0: TRACE:ms:SCO[4095] FSM State Transition: OK>PackSOAPHeader
192225.L375!GWWS.5732.5112.0: TRACE:ms:SCO[4095] FSM State Transition: Default>WSRMHandle3
192225.L375!GWWS.5732.5112.0: TRACE:ms:SCO[4095] FSM State Transition: OK>PackHTTP
192225.L375!GWWS.5732.5112.0: TRACE:ms:SCO[4095] FSM State Transition: Default>Send
192225.L375!GWWS.5732.5112.0: TRACE:ms:Sending HTTP Header: HTTP/1.1 500 Internal Server Error
Server: gSOAP/2.7
Content-Type: text/xml; charset=UTF-8
Content-Length: 398
Connection: close
192225.L375!GWWS.5732.5112.0: TRACE:ms:Sending SOAP Message: <?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAP-ENV:Fault><faultcode>SOAP-ENV:Client</faultcode><faultstring>GWWS_CAT:1034: DataMapping Error: Failed to parse tag 'tf32flat'.</faultstring></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
192225.L375!GWWS.5732.5112.0: TRACE:ms:SCO[4095] FSM State Transition: Default>Connecting
192225.L375!GWWS.5732.5112.0: TRACE:ms:SCO[4095] FSM State Transition: OK>SendToNet
192225.L375!GWWS.5732.5112.0: TRACE:ms:Send a http message to net, SCO index=4095
192225.L375!GWWS.5732.5112.0: TRACE:ms:SCO[4095] FSM State Transition: OK>SendOver
192225.L375!GWWS.5732.5112.0: TRACE:ms:SCO[4095] FSM State Transition: Inbound>WSRMHandle4
192225.L375!GWWS.5732.5112.0: TRACE:ms:SCO[4095] FSM State Transition: OK>Delete 
Ok, I have discovered that this is a question of decimal separator. My Windows system has by default Polish reginal settings, where the decimal sparator is "," opposite to "." for English. When I send the same Envelope with float values in format required by Tuxedo it works OK. But the question arises : how to change the Tuxedo to require other format ? The changing of regional settings to English does not work ? Does it reads them only during installation ?
regards Olek 
Hi OleK,
This is a known issue and has been fixed in SALT. Unfortunately it was fixed in SALT 1.1 and not propagated to the latest SALT version yet. I am not quite sure which version you are using. If you already bought SALT, you may ask your Oracle support person to ask a patch with fixing propagation. You can also work around this by,
Set the following registry key before starting Tuxedo.
[HKEY_USERS\.DEFAULT\Control Panel\International]
"sDecimal"=".
Regards,
Wayne 
Dear Wayne,
Thank again for you help !
This is my test/development environment. The target one will be on i5/i6/AIX so I will need to come back to the problem once again when the system will be about to run the pre-production tests.
regards Olek

tpstrerror: 'TPEITYPE - type and/or subtype do not match service's'

Hi,
I have a problem with reciving data from webservice by Salt while there is no inner xml tags in it. In response I got this:
tpcall (iResult:'-1', tpstrerror: 'TPEITYPE - type and/or subtype do not match service's')
Response in WSDL looks like this (fundAsset has minOccurs=0, and it is done the same in MIF file by automatic generation in wsdlcvt command):
     <xs:element name="getFundAssets">
                    <xs:complexType>
                         <xs:sequence>
                              <xs:element name="clientCode" type="xs:string"/>
                         </xs:sequence>
                    </xs:complexType>
               </xs:element>
               <xs:element name="getFundAssetsResponse">
                    <xs:complexType>
                         <xs:sequence>
                              <xs:element name="fundAssets" type="ns:FundAssets"/>
                         </xs:sequence>
                    </xs:complexType>
               </xs:element>
               <xs:complexType name="FundAssets">
                    <xs:sequence>
                         <xs:element maxOccurs="unbounded" minOccurs="0" name="fundAsset" nillable="true" type="ns:FundAsset"/>
                    </xs:sequence>
               </xs:complexType>
               <xs:complexType name="FundAsset">
                    <xs:sequence>
                         <xs:element name="name" type="xs:string"/>
                         <xs:element name="valuation" type="xs:double"/>
                         <xs:element name="currency" type="xs:string"/>
                    </xs:sequence>
               </xs:complexType>
Output data in WSDL looks like beneath. Service is used to get records from database. While there are no records only empty <fundAssets/> tag is returned. When there are records sets of <fundAsset/> are returned.
The problem with TPEITYPE occures only while there are no records in response. While there are <foundAsset> tags inside <fundAssets>- unparsing goes OK and I can easly take data after tpcall in my tuxedo service.
The return data (in ULOG) looks like this (while error):
<?xml version='1.0' encoding='UTF-8'?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<ns1:getFundAssetsResponse xmlns:ns1="http://www.aaa.com/webservices/types">
<fundAssets />
</ns1:getFundAssetsResponse>
Logs from ULOG:
180450.ibmwbk!GWWS.3584208.1036.0: TRACE:ms:parse_header_field() return 4
180450.ibmwbk!GWWS.3584208.1036.0: TRACE:ms:SCO[4095] FSM State Transition: NotFound>Receive
180450.ibmwbk!GWWS.3584208.1036.0: TRACE:ms:SCO[4095] FSM State Transition: WAKEUP>Receive
180450.ibmwbk!ud32.1978594.1.-2: TRACE:at: { tpgetrply(0xfffffffffffe390, 0xfffffffffffe3a0, 0xfffffffffffe398, 0x80)
180450.ibmwbk!GWWS.3584208.1036.0: TRACE:ms:SCO[4095] FSM State Transition: WAKEUP>Receive
180450.ibmwbk!GWWS.3584208.1036.0: TRACE:ms:SCO[4095] FSM State Transition: WAKEUP>Receive
180450.ibmwbk!GWWS.3584208.1036.0: TRACE:ms:SCO[4095] FSM State Transition: WAKEUP>Receive
180450.ibmwbk!GWWS.3584208.1036.0: TRACE:ms:SCO[4095] FSM State Transition: WAKEUP>Receive
180450.ibmwbk!GWWS.3584208.1036.0: TRACE:ms:SCO[4095] FSM State Transition: WAKEUP>Receive
180450.ibmwbk!GWWS.3584208.1036.0: TRACE:ms:SCO[4095] FSM State Transition: WAKEUP>Receive
180450.ibmwbk!GWWS.3584208.1036.0: TRACE:ms:SCO[4095] FSM State Transition: Found>ParseHTTP
180450.ibmwbk!GWWS.3584208.1036.0: TRACE:ms:HTTP Parsing: Buffer length 5 -- 0
180450.ibmwbk!GWWS.3584208.1036.0: TRACE:ms:SCO[4095] FSM State Transition: OK>HTTPDispatch
180450.ibmwbk!GWWS.3584208.1036.0: TRACE:ms:A HTTP message is received, SCO index=4095
180450.ibmwbk!GWWS.3584208.1036.0: TRACE:ms:SCO[4095] FSM State Transition: HTTPOK>ParseSOAPHeader
180450.ibmwbk!GWWS.3584208.1036.0: TRACE:ms:SCO[4095] FSM State Transition: Default>ParseHeaderRoot
180450.ibmwbk!GWWS.3584208.1036.0: TRACE:ms:A SOAP message is received, SCO index=4095
180450.ibmwbk!GWWS.3584208.1036.0: TRACE:ms:SCO[4095] FSM State Transition: None>ParseSOAPBody
180450.ibmwbk!GWWS.3584208.1036.0: TRACE:ms:SCO[4095] FSM State Transition: Default>ParseBodyRoot
180450.ibmwbk!GWWS.3584208.1036.0: TRACE:ms:SCO[4095] FSM State Transition: OK>ParseBodyElement
180450.ibmwbk!GWWS.3584208.1036.0: TRACE:ms:SCO[4095] FSM State Transition: OK>WSSEPolicyCheck1
180450.ibmwbk!GWWS.3584208.1036.0: TRACE:ms:SCO[4095] FSM State Transition: OK>WSRMHandle1
180450.ibmwbk!GWWS.3584208.1036.0: TRACE:ms:SCO[4095] FSM State Transition: Default>FindService
180450.ibmwbk!GWWS.3584208.1036.0: TRACE:ms:SCO[4095] FSM State Transition: OK>XML2Tux
180450.ibmwbk!GWWS.3584208.1036.0: TRACE:ms:SCO[4095] FSM State Transition: OBFail>Error
180450.ibmwbk!GWWS.3584208.1036.0: TRACE:ms:SCO[4095] FSM State Transition: Outbound>EnTuxedoQ
180450.ibmwbk!GWWS.3584208.1036.0: TRACE:ms:SCO[4095] FSM State Transition: Default>PutToCallingQ
180450.ibmwbk!GWWS.3584208.1291.0: TRACE:ms:SCO[4095] FSM State Transition: WAKEUP>EnTuxedoQ
180450.ibmwbk!WSSopoi.3518604.1.0: TRACE:at: } tpcall = -1 [tperrno TPEITYPE]
180450.ibmwbk!GWWS.3584208.1291.0: TRACE:ms:SCO[4095] FSM State Transition: WAKEUP>ReadyDeletion
180450.ibmwbk!WSSopoi.3518604.1.0: TRACE:at: { tpcall("inwLogSerwer", 0x1100dcdd8, 0, 0x110000e08, 0xfffffffffffe280, 0x0)
180450.ibmwbk!GWWS.3584208.1291.0: TRACE:ms:SCO[4095] FSM State Transition: OK>Delete
Where is the problem?
MIF file (as you can see there are requiredcount and count set to '0' so there should be no need to send <fundAsset> tag):
          param=fundAssets
          access=out
          paramschema=XSD_E:fundAssets#http://www.aaa.com/webservices/types
          type=fml32
          (
               param=fundAsset
               access=out
               paramschema=XSD_E:fundAsset#http://www.aaa.com/webservices/types
               requiredcount=0
               count=0
               type=fml32
               (
                    param=name
                    access=out
                    paramschema=XSD_E:name#http://www.aaa.com/webservices/types
                    type=string
                    primetype=string
                    param=valuation
                    access=out
                    paramschema=XSD_E:valuation#http://www.aaa.com/webservices/types
                    type=double
                    primetype=double
                    param=currency
                    access=out
                    paramschema=XSD_E:currency#http://www.aaa.com/webservices/types
                    type=string
                    primetype=string
               )
          )
FML file:
clientCode     1     string     -     fullname=clientCode, schema=xs:string
currency     2     string     -     fullname=currency, schema=xs:string
fundAsset     3     fml32     -     fullname=fundAsset, schema=ns:FundAsset
fundAssets     4     fml32     -     fullname=fundAssets, schema=ns:FundAssets
name     7     string     -     fullname=name, schema=xs:string
valuation     8     double     -     fullname=valuation, schema=xs:double
Maybe some fields are not recognized... Is there a diference between: <fundAssets /> and <fundAssets></fundAssets> ?
I got no more ideas... because while I got all data with <fundAsset> inside everything is OK.
Edited by: user9100925 on 2012-06-12 23:47 
hi,
Which version (for both SALT and tuxedo) and which platform you used?
Regards,
Xu He 
hi,
oslevel -g
AIX 5.3.0.60
wsadmin -v
INFO: Oracle SALT, Version 10.3.0.0, 64-bit, Patch Level (none)
INFO: Oracle Tuxedo, Version 10.3.0.0, 64-bit, Patch Level (none)
How can it be importand here? This is Salt 2.0, we had to upgrade from tuxedo 8.1 to tuxedo 10 because of new features in SALT 2.0 (vs 1.1). By upgarade I mean new instance of tuxedo (not upgradeing old codes).
Regards
Paul

GWWS_CAT:1068: DataMapping Error

Hi, I am seeing this very peculiar problem with my SALT installation. The below request when submitted will return a successful response, however, if the input parameters orders are changed I get the below error, any idea what is causing this? [Request]<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:pack.dvc05_typedef.salt11">   <SOAP-ENV:Header/>   <SOAP-ENV:Body>      <urn:csGtBanFinInfd5> <urn:inbuf> <urn:OPERATOR_ID>60001</urn:OPERATOR_ID> <urn:APPLICATION_ID>J</urn:APPLICATION_ID> <urn:TRANSACTION_MODE>O</urn:TRANSACTION_MODE> <urn:RUN_DATE>20160810</urn:RUN_DATE> <urn:MARKET_CODE>CAN</urn:MARKET_CODE> <urn:ENV_CODE>ENV05</urn:ENV_CODE> <urn:SESSION_ID>0</urn:SESSION_ID> <urn:ONLINE_TRX_NO>0</urn:ONLINE_TRX_NO> <urn:GN_SRC_CHANNEL>C</urn:GN_SRC_CHANNEL> <urn:BAN>492209799</urn:BAN> <urn:RUN_MODE>I</urn:RUN_MODE> </urn:inbuf>      </urn:csGtBanFinInfd5>   </SOAP-ENV:Body></SOAP-ENV:Envelope> [Response]<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">   <SOAP-ENV:Body>      <SOAP-ENV:Fault> <faultcode>SOAP-ENV:Client</faultcode> <faultstring>GWWS_CAT:1068: DataMapping Error: There is the redundant data in the received buffer.</faultstring>      </SOAP-ENV:Fault>   </SOAP-ENV:Body></SOAP-ENV:Envelope> [ULOG]...113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:SCO[4095] FSM State Transition: --WAKEUP-->Receive113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:SCO[4095] FSM State Transition: --Found-->ParseHTTP113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:HTTP Parsing: Buffer length 1107 -- POST /dvc05 HTTP/1.1Accept-Encoding: gzip,deflateContent-Type: text/xml;charset=UTF-8SOAPAction: "csGtBanFinInfd5"Content-Length: 856Host: vmbdcl005.rogers.com:22135Connection: Keep-AliveUser-Agent: Apache-HttpClient/4.1.1 (java 1.5)<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:pack.dvc05_typedef.salt11">   <SOAP-ENV:Header/>   <SOAP-ENV:Body>      <urn:csGtBanFinInfd5> <urn:inbuf> 113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:           <urn:OPERATOR_ID>60001</urn:OPERATOR_ID> <urn:APPLICATION_ID>J</urn:APPLICATION_ID> <urn:TRANSACTION_MODE>O</urn:TRANSACTION_MODE> <urn:RUN_DATE>20160810</urn:RUN_DATE> <urn:MARKET_CODE>CAN</urn:MARKET_CODE> <urn:ENV_CODE>ENV05</urn:ENV_CODE> <urn:SESSION_ID>0</urn:SESSION_ID> <urn:ONLINE_TRX_NO>0</urn:ONLINE_TRX_NO> <urn:GN_SRC_CHANNEL>C</urn:GN_SRC_CHANNEL> <urn:RUN_MODE>I</urn113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms::RUN_MODE> <urn:BAN>492209799</urn:BAN> </urn:inbuf>      </urn:csGtBanFinInfd5>   </SOAP-ENV:Body></SOAP-ENV:Envelope>113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:parse_header_field() return 7113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->HTTPDispatch113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:A HTTP message is received, SCO index=4095113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:Finding endpoint, soap->path is /dvc05, request_uri is /dvc05113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:SCO[4095] FSM State Transition: --Post-->ParseSOAPHeader113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:SCO[4095] FSM State Transition: --Default-->ParseHeaderRoot113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:A SOAP message is received, SCO index=4095113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:SCO[4095] FSM State Transition: --None-->ParseSOAPBody113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:SCO[4095] FSM State Transition: --Default-->ParseBodyRoot113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->ParseBodyElement113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:Begin data transformation of request message, buffer type = FML32, SCO index=4095113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->WSSEPolicyCheck1113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->WSRMHandle1113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->FindService113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->XML2Tux113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:<csGtBanFinInfd5> <csGtBanFinInfd5>:<inbound>:type<LONG>:schema-type<long>:minOccur<0>:maxOccur<0>:name<OPERATOR_ID>:value<60001>113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:<csGtBanFinInfd5> <csGtBanFinInfd5>:<inbound>:type<STRING>:schema-type<string>:minOccur<0>:maxOccur<0>:name<APPLICATION_ID>:value<J>113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:<csGtBanFinInfd5> <csGtBanFinInfd5>:<inbound>:type<CHAR>:schema-type<char>:minOccur<0>:maxOccur<0>:name<TRANSACTION_MODE>:value<0x4F>113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:<csGtBanFinInfd5> <csGtBanFinInfd5>:<inbound>:type<STRING>:schema-type<string>:minOccur<0>:maxOccur<0>:name<RUN_DATE>:value<20160810>113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:<csGtBanFinInfd5> <csGtBanFinInfd5>:<inbound>:type<STRING>:schema-type<string>:minOccur<0>:maxOccur<0>:name<MARKET_CODE>:value<CAN>113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:<csGtBanFinInfd5> <csGtBanFinInfd5>:<inbound>:type<STRING>:schema-type<string>:minOccur<0>:maxOccur<0>:name<ENV_CODE>:value<ENV05>113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:<csGtBanFinInfd5> <csGtBanFinInfd5>:<inbound>:type<LONG>:schema-type<long>:minOccur<0>:maxOccur<0>:name<SESSION_ID>:value<0>113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:<csGtBanFinInfd5> <csGtBanFinInfd5>:<inbound>:type<LONG>:schema-type<long>:minOccur<0>:maxOccur<0>:name<ONLINE_TRX_NO>:value<0>113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:<csGtBanFinInfd5> <csGtBanFinInfd5>:<inbound>:type<CHAR>:schema-type<char>:minOccur<0>:maxOccur<0>:name<GN_SRC_CHANNEL>:value<0x43>113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:<csGtBanFinInfd5> <csGtBanFinInfd5>:<inbound>:type<STRING>:schema-type<string>:minOccur<0>:maxOccur<0>:name<RUN_MODE>:value<I>113439.saltdom1!GWWS.6042.2951866112.0: processSoap2BufElem return error:<GWWS_CAT:1068: DataMapping Error: There is the redundant data in the received buffer.>113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:SCO[4095] FSM State Transition: --Fail-->SOAPFault113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->PackSOAPBody113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->PackSOAPHeader113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:SCO[4095] FSM State Transition: --Default-->WSRMHandle3113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->PackHTTP113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:SCO[4095] FSM State Transition: --Default-->Send113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:Sending HTTP Header: HTTP/1.1 500 Internal Server ErrorServer: gSOAP/2.7Content-Type: text/xml; charset=UTF-8Content-Length: 351Connection: close113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:Sending SOAP Message: <?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode>SOAP-ENV:Client</faultcode><faultstring>GWWS_CAT:1068: DataMapping Error: There is the redundant data in the received buffer.</faultstring></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:SCO[4095] FSM State Transition: --Default-->Connecting113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->SendToNet113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:Send a http message to net, SCO index=4095113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->SendOver113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:SCO[4095] FSM State Transition: --Inbound-->WSRMHandle4113439.saltdom1!GWWS.6042.2951866112.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->Delete  Thanks.Ransford

Question about using XA-transactions with Oracle SALT

Hello.. I've run into problems setting up a SALT environment with XA-transactions.I've followed the documentation found at Configuring a SALT Application but I can't get transactions to work properly. When calling a Tuxedo service from a simple web-application through SALT, the gateway always responds with "GWWS_CAT:1354: ERROR: The Web Services gateway is not configured to support WS-TX transactions." The log printed to ULOG is as follows:==============================================================================================================================095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:SCO[4095] FSM State Transition: --WAKEUP-->Created 095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:SCO[4095] FSM State Transition: --Inbound-->Receive 095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:SCO[4095] FSM State Transition: --Found-->ParseHTTP 095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:HTTP Parsing: Buffer length 1573 -- POST /compapp HTTP/1.1Accept: text/xml, multipart/relatedContent-Type: text/xml; charset=utf-8SOAPAction: "dbService1"User-Agent: Metro/2.3 (tags/2.3-7528; 2013-04-29T19:34:10+0000) JAXWS-RI/2.2.8 JAXWS/2.2 svn-revision#unknownCache-Control: no-cachePragma: no-cacheHost: tuxnix1:8080Connection: keep-aliveContent-Length: 1225  <?xml version='1.0' encoding='UTF-8'?><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Header><Coo 095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:rdinationContext xmlns="http://docs.oasis-open.org/ws-tx/wscoor/2006/06" xmlns:ns2="http://www.w3.org/2005/08/addressing" xmlns:ns3="http://schemas.xmlsoap.org/soap/envelope/" ns3:mustUnderstand="1"><Identifier>urn:uuid:4D2-313431303135393134363632382D30</Identifier><Expires>0</Expires><CoordinationType>http://docs.oasis-open.org/ws-tx/wsat/2006/06</CoordinationType><RegistrationService><ns2:Address>http://WL2013170.eu.tieto.com:8080/__wstx-services/RegistrationPortTypeRPC11</ns2:Address><ns2:Re 095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:ferenceParameters><wsat-wsat:txId xmlns:wsat-wsat="http://com.sun.xml.ws.tx.at/ws/2008/10/wsat" xmlns:wsa="http://www.w3.org/2005/08/addressing">4D2-313431303135393134363632382D30</wsat-wsat:txId><wsat-wsat:routing xmlns:wsat-wsat="http://com.sun.xml.ws.tx.at/ws/2008/10/wsat" xmlns:wsa="http://www.w3.org/2005/08/addressing">none</wsat-wsat:routing></ns2:ReferenceParameters></RegistrationService></CoordinationContext></S:Header><S:Body><dbService1 xmlns="urn:pack.compapp_typedef.salt11"><inbuf><S 095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:TR4_Message>Test message</STR4_Message><STR4_Status></STR4_Status></inbuf></dbService1></S:Body></S:Envelope> 095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:parse_header_field() return 9 095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->HTTPDispatch 095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:A HTTP message is received, SCO index=4095095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:Finding endpoint, soap->path is /compapp, request_uri is /compapp 095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:SCO[4095] FSM State Transition: --Post-->ParseSOAPHeader 095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:SCO[4095] FSM State Transition: --Default-->ParseHeaderRoot 095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:A SOAP message is received, SCO index=4095095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->ParseHeaderElement 095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:SCO[4095] FSM State Transition: --None-->WSCOORCheck 095227.tuxnix1!GWWS.22994.2885678848.0: GWWS_CAT:1354: ERROR: The Web Services gateway is not configured to support WS-TX transactions.095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:SCO[4095] FSM State Transition: --Fail-->SOAPFault 095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->PackSOAPBody 095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->PackSOAPHeader 095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:SCO[4095] FSM State Transition: --Default-->WSRMHandle3 095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->PackHTTP 095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:SCO[4095] FSM State Transition: --Default-->Send 095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:Sending HTTP Header: HTTP/1.1 500 Internal Server ErrorServer: gSOAP/2.7Content-Type: text/xml; charset=utf-8Content-Length: 399Connection: keep-alive  095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:Sending SOAP Message: <?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header></SOAP-ENV:Header><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode>wscoor:InvalidState</faultcode><faultstring>GWWS_CAT:1353: The message was invalid for the current state of the activity.</faultstring><detail></detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope> 095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:SCO[4095] FSM State Transition: --Default-->Connecting 095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->SendToNet 095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:Send a http message to net, SCO index=4095095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->SendOver 095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:SCO[4095] FSM State Transition: --Inbound-->WSRMHandle4 095227.tuxnix1!GWWS.22994.2885678848.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->Delete ============================================================================================================================== The error message "wscoor:InvalidState" in the response seems to indicate a problem with the transaction log. In the aforementioned configuration documentation, there is a note of this in the Error Conditions-section: No log file is configured for the gateway. A wscoor:InvalidState fault is sent back to the caller. The Detail field contains a corresponding message. My question is, what other steps are required for configuring the log file than are noted in the configuration documentation (that is, adding the TLogDevice and TLogName to the SALT-configuration file)? My SALT-configuration file is as follows:=========================================================================<Deployment xmlns="http://www.bea.com/Tuxedo/SALTDEPLOY/2007">     <WSDF>          <Import location="/home/tuxadmin/tuxInstance/compapp.wsdf"></Import>     </WSDF>     <WSGateway>          <GWInstance id="GWWS1">               <TLogDevice location="/home/tuxadmin/tuxInstance/logs/GWWSTLOG"/>               <TLogName id="GWWS1TLOG"/>               <Inbound>                    <Binding ref="compapp:compapp_Binding">                         <Endpoint use="compapp_GWWS1_HTTPPort"></Endpoint>                    </Binding>               </Inbound>               <Properties>                    <Property name="enableSOAPValidation" value="true"/>               </Properties>          </GWInstance>     </WSGateway>     <System></System></Deployment>========================================================================= And UBBCONFIG:=========================================================================     *RESOURCES     IPCKEY          111111      MASTER          FRONTEND     MAXACCESSERS    100     MAXSERVERS      100     MAXSERVICES     100     MODEL           SHM     LDBAL           N      *MACHINES     tuxnix1    LMID=FRONTEND                    TUXCONFIG="/home/tuxadmin/tuxInstance/TUXCONFIG"                     TUXDIR="/opt/oracle/tuxedo12.1.1.0"                    APPDIR="/home/tuxadmin/tuxInstance/"                    TYPE="linux"                      ULOGPFX="/home/tuxadmin/tuxInstance/logs/ULOG"                     MAXWSCLIENTS=50      *GROUPS     LDMGRP GRPNO=1 LMID=FRONTEND     LGWGRP GRPNO=2 LMID=FRONTEND     SALTGRP GRPNO=3 LMID=FRONTEND      *SERVERS     DMADM SRVGRP=LDMGRP SRVID=1     GWADM SRVGRP=LGWGRP SRVID=1     GWTDOMAIN SRVGRP=LGWGRP SRVID=2 REPLYQ=N      TMMETADATA SRVGRP=SALTGRP SRVID=4 CLOPT="-A -- -f mdr_compapp.repos"     GWWS SRVGRP=SALTGRP SRVID=5 CLOPT="-A -- -iGWWS1"      *SERVICES========================================================================= Any help regarding this matter is much appreciated, thank you. Best regards,Tuomo Aalto
Hi Tuomo, to be honest with you I don't know too much about SALT but I think your problem may be related to the fact that your underpinning Tuxedo configuration doesn't seem to support transactions, so I guess it would be a challenge for GWWS to do it by itself. Try following the directions here:Configuring Your ATMI Application to Use Transactions and see if that will make things work better for you. This particular link is for Tuxedo 12 but for all practical purposes the steps have been the same since 6.0 (or probably even before that, but that's beyond my knowledge ). Hope this helps,/Per

Categories

Resources