topic Re: PriviligedActionException at tSOAP component, in SoapUI works fine in Talend Studio

PriviligedActionException at tSOAP component, in SoapUI works fine

Anonymous — Thu, 31 May 2018 14:58:14 GMT

Hi all,

I've build a small job, which just extracts values from one XML and fills with those values a SOAP request for a webservice.

However, when I run it, it gives an error, PriviligedActionException. While if I log the request and put it in SoapUI, then I get a succes response.

What could be causing this difference between using tSOAP in Talend and just using SoapUI? There is no authentication needed or anything, and I just put the whole request including Header in Talend. I hope you can help me!

This is the errormessage I get:

SEVERE: SAAJ0009: Message send failed
Exception in component tSOAP_1 (PIM)
com.sun.xml.messaging.saaj.SOAPExceptionImpl: java.security.PrivilegedActionException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed

To see the whole post, download it here

Re: PriviligedActionException at tSOAP component, in SoapUI works fine

Anonymous — Tue, 03 Jul 2018 08:57:36 GMT

Hello,

Please post some job setting screenshots on forum which will get more visibility and more help.

Best regards

Sabrina

Re: PriviligedActionException at tSOAP component, in SoapUI works fine

A_Froggatt — Wed, 04 Jul 2018 08:59:40 GMT

Is your SOAP endpoint a HTTPS one? If so you'll need to set up a truststore with the certificate and use tSetKeystore to connect to it. We have ours as part of the prejob flow so the job can use it properly.

SoapUI and Postman can both disregard self-signed certificates but Talend doesn't. It's also worth pointing out that the certificate's hostname must match the URL of the SOAP endpoint, one selfsigned to localhost won't work.

Oracle have a good truststore guide here, then the Talend reference docs for tSetKeystore should work for the rest.

Re: PriviligedActionException at tSOAP component, in SoapUI works fine

Anonymous — Thu, 05 Jul 2018 09:32:24 GMT

are you using ..asmx?wsdl as your endpoint

your soap action is in the wsdl

output in document

put xml in between " "

replace all " with ' inside XML