Hi ,
FYI, you can find the how to set the timeout parameters here [1]
[1] http://cwiki.apache.org/CXF20DOC/client-http-transport.html
Willem.
Glen Mazza wrote:
I'm not sure how to adjust the timeout parameters--someone else can
perhaps respond to that issue.
But how long should it take your server to respond? Can you greatly
simplify your server so it responds immediately (basically just mock it
out so it immediately returns something), to confirm that the 60-second
timeout is the real problem (as opposed to the client simply not being
able to access the server)?
The error you're getting: "Caused by: org.apache.cxf.interceptor.Fault:
Could not send Message." normally occurs to me when the server is
inaccessible for some reason, it can't be reached at all--not just a
time-out issue. Are you sure the URL in the WSDL (which I assume your
client is reading) is correct? If you call
http://localhost:8080/mywarfilename/myservice?wsdl, for example, do you
see the WSDL file in the browser?
HTH,
Glen
Am Sonntag, den 21.10.2007, 19:15 -0600 schrieb Shen, Minsheng
(MinSheng):
Hi All,
I am new to this mail list.
I am developing a web service using CXF 2.0.2. Everything is tested
and
works fine on the service side. I used wsdl2java to create a client.
When I invoke the client, I got "Interceptor has thrown exception,
unwinding now
org.apache.cxf.interceptor.Fault: Could not send Message."
I believe on the client side the default time out for reading message
is
60 seconds and this error is caused by read time out. The following is
the stacktrace. Any help you can provide will be greatly appreciated!!
Thank you in advance!
-Minsheng
INFO: Interceptor has thrown exception, unwinding now
org.apache.cxf.interceptor.Fault: Could not send Message.
Caused by: java.net.SocketTimeoutException: Read timed out
