My Oracle Support Banner

Tuxedo Outbound Web Service tpcall() Failing TPEITYPE - Error Parsing XML Payload. (Doc ID 1348553.1)

Last updated on SEPTEMBER 13, 2021

Applies to:

Oracle Tuxedo - Version 9.1 to
Information in this document applies to any platform.


Getting a tperrno=TPEITYPE failure when executing a tpcall() to a  webservice from a native client.

NOTE:  The attribute values used in this article represent fictitious sample names that are made up as example. Any similarity to actual code, is purely coincidental and not intended in any other manner.

The corresponding tpstrerror() output by the client is as follows:

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

(A similar error occurs using ud32 to call the webservice.)

The ULOG shows the XML response message from the webservice as:

<SOAP-ENV:Envelope xmlns:SOAP-ENV="" xmlns:xsi="" xmlns:xsd="
<SOAP-ENV:Body> <ns:getServiceResponse xmlns:ns='http://<hostname.domain>/MyServices'>
<get:GetServiceResponse xmlns:get='http://<hostname.domain>/schemas/GetService'>

Right after that in the ULOG a failure is reported when GWWS tries to execute the conversion from XML to a Tuxedo FML32 buffer:

074046.TuxMachineName! TRACE:ms:SCO[4095] FSM State Transition:--Default-->FindService
074046.TuxMachineName! TRACE:ms:SCO[4095] FSM State Transition: --OK-->XML2Tux
074046.TuxMachineName! TRACE:ms:SCO[4095] FSM State Transition: --OBFail-->Error




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.