Weird behaviour in Axiom XML Parsing (Guththila)

[alexis-gruet-deel]

Dear experts,

A quick question,

We observed, for some identified soap request payload, truncated XML in response.

We use guththila as the main XML parser.

This is confirmed by :

om_stax_builder.c(651) -1 returned from the xml reader when reading xml

a token return -1

Do you have experienced similar issues ?

[ghost]

Can you trace the network to determine the source of the missing data using something like Wireshark or Fiddler2?

[alexis-gruet-deel]

Thank you @cxsup2 for your help.

I forgot to mention that i use axis2 from the trunk, not the unofficial ... so maybe this is the wrong place.

hard to wireshark the network as the response is encrypted by SSL.

However, i have the missing XML Nodes ( did it through a dumb diff ) Maybe you will observe a bad char that can lead to this issue :

643.                <tplClaimsCountLastYear>
644.                   <id>1</id>
645.                   <sortOrder>0</sortOrder>
646.                   <WIDefault>false</WIDefault>
647.                </tplClaimsCountLastYear>
648.                <tplInsuranceYearsCount>
649.                   <id>1</id>
650.                   <sortOrder>0</sortOrder>
651.                   <WIDefault>false</WIDefault>
652.                </tplInsuranceYearsCount>

and

654.             <roleId>6</roleId>

and also

656.              <policyType>1</policyType>
657.          <productId>20037</productId>
658.          <rawCalculation>false</rawCalculation>
659.          <rsi>true</rsi>
660.          <stamp>-760213244;156109955;;</stamp>
661.          <startDate>2017-10-20T00:00:00+02:00</startDate>
662.          <statusId>10</statusId>
663.          <ufg>false</ufg>
664.          <ufgRequestedForOfferInCurrentFlow>false</ufgRequestedForOfferInCurrentFlow>
665.          <url>https://1.1.1.1/kalkulator_ubezpieczenia_OC_AC_2/oferta/null-null</url>

[ghost]

If you're on Windows, Fiddler2 will support tracing SSL. A few things:

• I'd use axis2c-unofficial since it has a better maintenance record
• Yes, you should be reporting axis2c related issues in the axis2c project

Given your description of missing nodes, it seems like the payload isn't be constructed properly. It should be easy enough to inspect the XML string prior to submitting to the generated SOAP proxy class. I use tinyxml2 to build and encode the XML payload.