You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Craig <su...@gmail.com> on 2008/10/01 07:19:12 UTC

Re: trying to catch timeout exception on client side

I got a bounce from ezmlm...not sure if this went through.

On Tue, Sep 30, 2008 at 9:02 AM, Craig <su...@gmail.com> wrote:
> Hi all,
>
> disclaimer: very new to CXF, and slightly confused by the Interceptor concept.
>
> I am simply trying to tell if my client side soap call failed because
> of a socket
> timeout. Unfortunately, the exception that gets thrown doesn't seem to
> know anything about the timeout. I am able to catch a
> WebServiceException, that has a SOAPException embedded as the cause,
> that says "Unable to create SOAP factory.", which doesn't really help
> me.
>
> I know the timeout is causing the error because a) I set the timeout
> to 1ms, and b) CXF (via jboss) is logging it in the eclipse console, e.g.
>
> org.apache.cxf.interceptor.Fault: Read timed out
> ...
> Caused by: java.net.SocketTimeoutException: Read timed out
>
>
> How can I find out in my code what CXF apparently knows but doesn't tell me?
>
>
> Many thanks,
> Craig
>
>
>
> Here is a code snippet:
>
> JaxWsProxyFactoryBean myServiceService = new JaxWsProxyFactoryBean();
> myServiceService.setServiceClass(...);
> myServiceService.setAddress(...)
> myServiceProxy = (MyService)myServiceService.create();
>
> try {
>  myServiceProxy.mySoapMethod();
> }
> catch(WebServiceException e) {
>  //e doesn't seem to tell me anything about the timeout????? How can
> I get a more specific exception?
> }
>