Error with tESBConsumer component in sub-job: Unexpected wrapper element found

[FPenco1666863018]

Hello everyone,

I am experiencing an issue with the tESBConsumer component in my sub-jobs. When I attempt to run the parent job, I receive the following error:

Fault {string: Unexpected wrapper element {http://www.w3.org/2003/05/soap-envelope}Envelope found. Expected {http://{URL_STRING_HIDDEN]}searchEvents.; code:{http://schemas.xmlsoap.org/soap/envelope/}Client}

The error indicates that my SOAP request is receiving an Envelope element instead of the expected searchEvents element.

I have found that if I run each sub-job individually before running the parent job, everything works correctly.

This suggests that there is an initialization step that occurs when launching each sub-job that does not occur when I run the parent job.

Additionally, if I don't perform this operation before building the job, I get the error message. And every time I close Talend and reopen it, I need to repeat this operation.

I would like to understand why this is happening and how I can resolve this issue without having to manually run each sub-job.

Has anyone else encountered this issue or have any idea what might be causing this error?

Thank you in advance for your help.

Talend : Talend Open Studio for Data Integration 8.0.1

OS : Windows or Linux

Best regards,

[Anonymous]

Hi

Can you share a screenshot of parent job? I want to see how you arrange the execution order of sub-jobs in parent job.

Regards

Shong

[FPenco1666863018]

HI @Shicong Hong​ 

Sorry for the very late response 🙂

Nevertheless, I still have this error no matter the job.

Here is a part of the parent job that calls the subjob "getTechniciansStatusMulti":

 

In this subjob, I send my prepared XML envelope as a string:

 

And here is my child job:

 

The tLibraryLoad is used to load the library: saaj-impl-1.5.2.jar (Without this, it won't work)

The tFixedFlowInput retrieves the context payload, converts it into a document, and sends it to tESBConsumer as input.

Then, I process the return.

So, as I was saying, if I don't open this job before launching/building the parent, the job gives me an error as indicated in the first message.

Thanks for your help,

[Anonymous]

@Florent Penco , how many sub-jobs are called in the parent job? If you use tLibraryLoad components to load external jars in sub-jobs, consider loading these jars in the beginning of parent job.

[FPenco1666863018]

@Shicong Hong​ , I have about 10 sub-jobs, and 4 of them are affected. However, it's not about the number of sub-jobs, because even with a parent job and 1 sub-job, it's the same issue.

I moved the tLibraryLoad to the parent job and removed the entry in the sub-jobs, but it's still the same problem.

Where could this be coming from? The WSDL? Because I can't understand at all why I have to open the sub-job first. I've tried many things; otherwise, the solution is to replace the tESBConsumer with a tSOAP.

But the tESBConsumer is supposed to load the corresponding WSDL.

[Anonymous]

You mentioned "it works with tSOAP component", what is the soap version you selected on tSOAP? if it is the default version 1.1, can you try with 1.2 to see if it works also?

[FPenco1666863018]

I use SOAP 1.2 with tSOAP, and I send XML with SOAP 1.2 using tESBConsumer.

This works well because, for example, I have another job with a sub-job containing tSOAP, and I don't need to open it before running or building the job.

I tried to search for information about tESBConsumer. I thought it might be related to my XML, but it is well-formed and compliant with SOAP 1.2 recommendations.

[FPenco1666863018]

Hi,

Do you have any recommandations ? I have the same problem. See my last answer

Thanks,