[resolved] tSOAP Message send failed

[Anonymous]

Hello everybody,
I'm trying to call a web-service with the help of tSOAP. At the moment my job only exists of one tSOAP with the (hopefully correct) configurations to my web-service and a tLogRow Component. Now when executing the job, I get the following error:
com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection post
Schwerwiegend: SAAJ0009: Message send failed
Exception in component tSOAP_1
com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: Message send failed
at com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection.call(Unknown Source)
at org.talend.soap.SOAPUtil.invokeSOAP(SOAPUtil.java:109)
at portaldwjobs.prokon_habilkon_0_1.Prokon_Habilkon.tSOAP_1Process(Prokon_Habilkon.java:591)
at portaldwjobs.prokon_habilkon_0_1.Prokon_Habilkon.runJobInTOS(Prokon_Habilkon.java:900)
at portaldwjobs.prokon_habilkon_0_1.Prokon_Habilkon.main(Prokon_Habilkon

To see the whole post, download it here

[Anonymous]

Hey great. Thanks. Now I don't get any error anymore, but now nothing is happening. It just running for a long time with this message in the console:

connecting to socket on port 3627
connected

and then giving me a "unhandled event loop exception - no more handles" error. What does this error mean and how can I fix it?

[Anonymous]

Hi,
Does it work fine when you re-run job/ re-start studio? Is it random?
Any error log for it?
Best regards
Sabrina

[Anonymous]

It even asks me to restart the studio. But when doing so it always appears again when then restarting the job. And this everytime I start it.
Where do I find the error log?
I changed the memory parameters of the studio in the .ini file to try if it is related to that, but it doesn't change anything. Can you tell me what this error eyxactly wants to tell me?
Thanks for all the help.

[Anonymous]

Hi,

I changed the memory parameters of the studio in the .ini file to try if it is related to that, but it doesn't change anything. Can you tell me what this error eyxactly wants to tell me?

Yes, usually the error indicates you should set xms, xmx parameter in JVM. Is it a large job in studio? Did you set the "Use specific JVM arguments" in Advanced setting of Run review?(This change will only apply for the active Job.)
In addition that, error log is located in /workspace/.metadata/.log .
Best regards
Sabrina

[Anonymous]

Thanks. This seems to solve my problem completely.
But to still answer your question, it is a (I think) tiny job only consisting of the tSetKeystore compontent and a tSoap component (getting about 7MB data) and a tRow component. That's all.
I now set the paramaters in the advanced settings as follows:
-Xms 1024M
-Xmx1024M
-XX:MaxPermSize=256M
which was default when opening the tab. When reducing the Xms parameter to 256M it still doesn't work. Can you tell me why so I can understand it and apply it to future work?

[Anonymous]

Hi,

I changed the memory parameters of the studio in the .ini file to try if it is related to that

What you have done is effective for all Jobs. The default setting should be sufficient for all normal Job executions, therefore this global change of JVM arguments is not recommended.
Running a Job which processes a very large amount of data also cause memory issue, for talend client will cache items in memory (like a good java program should) and so you will see it gradually use more and more until it reaches the configured heap size.
So it is suggested that you should allocate more memory for the Job to be able to process large amounts of data or avoid memory issue.
Surely, to make most of talend product, there is a requirement on your hardware and software.
TalendHelpCenter:Installation+requirements.

I now set the paramaters in the advanced settings as follows:
-Xms 1024M
-Xmx1024M
-XX:MaxPermSize=256M
which was default when opening the tab. When reducing the Xms parameter to 256M it still doesn't work. Can you tell me why so I can understand it and apply it to future work?

What's the RAM size of your machine configuration? Why did you reduce it?
Best regards
Sabrina

[Anonymous]

The RAM size of my machine is 3GB.
I reduced it because I learned, that the Xms parameter is the size of the memory given at the start and Xmx is the max size to which the memory can grow during execution. And thus the Xms usually is smaller than Xmx. But here I need to set it to the same size and I don't understand it, because even when starting with a smaller memory it still has the possibility to reach up to the upper bound. Can you get what my question is?

[Anonymous]

Hi,
Is it working when you set the -Xms as 512M? There might be a conflict when -Xms is as same as -XX:MaxPermSize. The range of - Xms should be 256M-1024M.
The parameter:
-Xms 1024M
-Xmx1024M
-XX:MaxPermSize=256M
That means you give the max value to -Xms (1024M).
Best regards
Sabrina

[Anonymous]

Yes, when I set Xms to 512M it also works. So the min memory size this jobs needs to start is 512M?
And just to be sure. What do you mean with
"There might be a conflict when -Xms is as same as -XX:MaxPermSize."
becuase this also works in my case. Setting both (Xms and Xmx) to 1024M works.

[Anonymous]

Hi,
If -XX:MaxPermSize=256M is as same as your -Xms(reduce from1024 to 256), there might be a conflict.
For JVM parameter setting, there is no standard answer. It totally depends on your designed job and the number of processing data.
Best regards
Sabrina