WSDL deserialization failed!

[Former Member]

Hi,

I'm trying to consume a webservice provided by an AS Java Server on an application running on my server, also AS Java. While executing my application, i got an error explained mainly by:

Caused by: com.sap.engine.services.webservices.espbase.query.exceptions.TechnicalException: Deserializing xml stream http://<host>:<port>/bpem/testsapcom2Fglx2Ftutorial2Fpm22FPool2FPurchaseProcessContinuation1258a3ef1... failed.com.sap.engine.services.webservices.espbase.wsdl.exceptions.WSDLException: Read timed out

In fact, when i'm entering the url in my browser, i could read the WSDL without problem.

Could someone help me on that, and tell me where is the error and what to do to fix that. Thanks a lot.

Best Regards,

Jean NKENG

[Former Member · Accepted solution]

Jean,

Did you find a solution to this problem? I'm running into the same issue and don't know how to fix it.

Thanks,

-Tamara

[Former Member · Accepted solution]

I found the solution Tamara. In fact, when i changed the computer full name by the IP in the WSDL url, (if i understood) it seems like the WS host corresponding to the IP i entered was acting like a proxy or something like that, trying to reach another computer, this is why the connection timed out, and because it is the host, it normally doesn't need to reach another computer or server.

The solution is to keep the computer full name in the WSDL, but add the ip address corresponding to the computer full name in the hosts file of windows, located by default here:

Windows NT/2000/XP/2003/Vista: %SystemRoot%\system32\drivers\etc\hosts

Wiki page: http://en.wikipedia.org/wiki/Hosts_file.

Just add a line to the file:

<IP address> <Computer Full Name> (Separated by tabulation)

Cheers,

Jean

[Former Member]

I understood, nobody's interested

[Former Member]

Hi,

>I understood, nobody's interested

Do you understand that sending a question here is like sending a messsage in a bottle ?

For me, It is not a question of interest but I just never had this need and problem and so have no usefull answer to give.

Regards,

Olivier

[Former Member]

I have increased the socket timeout, and now, i got an http 502 error. In fact, the WSDL url was:

http://<Full computer name>:<Port>/bpem/testsapcom2Fglx2Ftutorial2Fpm22FPool2FPurchaseProcessContinuation1258a3ef18c4b6a9bec22e5a9cb4abef?wsdl

but i changed it to

http://<IP adress>:<Port>/bpem/testsapcom2Fglx2Ftutorial2Fpm22FPool2FPurchaseProcessContinuation1258a3ef18c4b6a9bec22e5a9cb4abef?wsdl

Because without that change, i can't even see the WSDL in my browser, due to the fact that my computer doesn't know how to connect to the computer with the name <Full Computer Name>, although the two computers are in the same domain.

Please Help!!!!!!!!!!!!!!