on 08-16-2010 1:00 PM
Dear All,
My System is SAP NetWeaver CE Ehp1 7.1 SP3.
1. I publish the service from ECC to CE.
2. I test the service in Services Registry which is well.
3. when I use it in web dynpro , I met this error:
com.sap.tc.webdynpro.model.webservice.api.WDWSModelExecuteException: Exception on execution of web service on destination 'zadd' for operation 'Zgaoservice' in interface '{urn:sap-com:document:sap:soap:functions:mc-style}ZADD'
At Web Services Logging & Tracing, I find this error:
-
Error com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding # Connection IO Exception. Check nested exception for details. (HTTP Client, does not have endpoint url specified.)
[EXCEPTION]
com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Connection IO Exception. Check nested exception for details. (HTTP Client, does not have endpoint url specified.)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.outputSOAPMessage(SOAPTransportBinding.java:401)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1132)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:818)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:759)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
It seems there is some error with your Web Service request. Test your service using WS Navigator or XML Spy or any other Web Service testing tool. To test use the WSDL you have mentioned in your third post or download the WSDL from the same URL.
Finally check in Web Service Logs and traces if the service call worked fine when tested from WS Navigator or some other tool.
Regards,
Avishek.
Hi Jiandong,
Are you in a clustered environment? You may need to upgrade to SP5 to resolve, there were quite a few WS inconsistencies resolved with SP5.
If you can't upgrade right now, and you're in a clustered environment, refer to SAP Note 1431669 for a possible workaround. It's not exactly the same error you're seeing but your error could also be caused by an "Inconsistency of WS container in cluster environment".
Also refer to the forum posting for a possible solution:
Regards, Trevor
Dear Avishek,
The error is same like it:
ebservices.espbase.client.bindings.impl.SOAPTransportBinding # Connection IO Exception. Check nested exception for details. (HTTP Client, does not have endpoint url specified.).
[EXCEPTION]
com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Connection IO Exception. Check nested exception for details. (HTTP Client, does not have endpoint url specified.).
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.outputSOAPMessage(SOAPTransportBinding.java:410)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1268)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:938)
Hello jiandong
This service url is not really the service url, it is the WSDL url (the definition only).
When you configure the service execution endpoint you need to point to an url like this
[http://host:port/sap/bc/srt/xip/sap/service_name/client/service_binding]. You can find it into your WSLD under the tag "SOAP Address Location"
hope this helps!
regards
roberti
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.