tESBProviderResponse UTF8 MalformedByteSequenceException

[MS5]

Hello all, 

We've developped a service SOAP in Talend (7.3 Open Studio) that need to respond using UTF-8 encoding. 

But for now, when executing a request or validated a response in SOAPUI or Oracle tool, the error below is triggered : 

Error occured in Studio and in Talend ESB Runtime.

But when the webservice is requested from a talend job, we can see <?xml version="1.0" encoding="UTF-8"?> and encoding is correct.

 

We have tried : 

• add java option -Dfile.encoding=UTF8 when starting the JVM
• transform every temp file in UTF-8
• verifying that the wsdl contain <?xml version="1.0" encoding="UTF-8"?> (it's the case)

Did anyone already have this issue? And what is the solution applied in this case?

Thank you,

[Anonymous]

Hello,

Is a successful response received from the tSOAP component?

Best regards

Sabrina

[MS5]

Hello Sabrina,

When we try to request the webservice using a tSoap, we receive a correct answer, the same we receive using a tEsbConsumer.

But in external tool, like OPA or SoapUi, the issue MalformedByteSequenceException appears.

Best regards,

[gjeremy1617088143]

Hi, maybe you have to configure utf 8 encoding, in your talend runtime.

Send me Love and Kudos

[Anonymous]

Hello,

Are you calling the Oracle service? Would you mind showing the full error stack trace?

Best regards

Sabrina

[MS5]

In Talend Runtime, we added the option  -Dfile.encoding=UTF8.

Is it enough?

[MS5]

Hello,

As the issue don't occur only in Oracle but also in SOAPUI, we didn't contact any support yet.

The stacktrace is the same in every external tool :

com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Octet 2 de la séquence UTF-8 à 3 octets non valide.

org.wsi.test.validator.ValidatorException: com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Octet 2 de la séquence UTF-8 à 3 octets non valide.

at org.wsi.test.validator.bsp10.SecureEnvelopeArtifact.validate(Unknown Source)

at org.wsi.test.validator.Artifacts.validateAll(Artifacts.java:31)

at org.wsi.test.validator.Validator.runValidation(Validator.java:63)

at org.wsi.test.validator.Validator.main(Validator.java:164)

Caused by: com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Octet 2 de la séquence UTF-8 à 3 octets non valide.

at com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.invalidByte(UTF8Reader.java:702)

at com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.read(UTF8Reader.java:409)

at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.load(XMLEntityScanner.java:1895)

at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.scanLiteral(XMLEntityScanner.java:1187)

at com.sun.org.apache.xerces.internal.impl.XMLScanner.scanAttributeValue(XMLScanner.java:987)

at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanAttribute(XMLNSDocumentScannerImpl.java:448)

at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:251)

at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2784)

at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:602)

at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:113)

at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:505)

at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:842)

at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:771)

at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:142)

at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:244)

at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:339)

at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121)

... 4 more

[Anonymous]

Hello,

We met this similar issue about tESBConsumer before and it is fixed in V 7.1.

It seems it is working when you use tsoap and tESBConsumer in talend?

Best regards

Sabrina

[MS5]

Hello,

I agree it works using Talend comopnents, but the goal is to use this webservice with an external tool.

I will test with a previous version of Talend if the issue occur also and let you know.

Best regards,

[Anonymous]

Hello,

It is a little hard for us to repro this issue with an external tool. Feel free to let us know if the issue occur also with a previous version of talend.

Best regards

Sabrina