[jira] [Resolved] (CXF-2208) Local Transport Client Timeout can't be configured

["Daniel Kulp (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CXF-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kulp resolved CXF-2208.
------------------------------

       Resolution: Won't Fix
    Fix Version/s: Invalid


This improvement request has been open for over a year and no-one has stepped up to implement it. As such, it does not seems to be a priority for the existing CXF community. If, in the future, someone would like to tackle this, feel free to open is and attach a patch.

> Local Transport Client Timeout can't be configured
> --------------------------------------------------
>
>                 Key: CXF-2208
>                 URL: https://issues.apache.org/jira/browse/CXF-2208
>             Project: CXF
>          Issue Type: Improvement
>          Components: Transports
>    Affects Versions: 2.0.9
>         Environment: This should apply also to 2.0.11, 2.1.X and 2.2.X, as the code in question seems to be in common.
>            Reporter: Kaj Kandler
>             Fix For: Invalid
>
>
> When debugging with a local transport it times out after 60 s.  Here is Dan's comment to the question:
> I think you are hitting the timeout  in the client impl that is used when
> doing synchronous calls over an async transport.   The local transport is, by
> default, an async transport.  
> There are two options:
> 1) Get the ClientImpl from the proxy and call the setSynchronousTimeout method
> on it.
> 2) Flip the local transport to run in direct dispatch mode.  Basically, to the
> request context, put:
> LocalConduit.DIRECT_DISPATCH, Boolean.TRUE
> Unfortunately, it doesn't look like either is configurable via spring.  
> Possible log some bugs (and some patches :-).    The second should be easy.  I
> THINK just changing the call in LocalConduit of:
> message.get(DIRECT_DISPATCH)
> to:
> message.getContextualProperty(DIRECT_DISPATCH)
> should allow it to be set with the jaxws:properties stuff on the client stuff
> in the spring config.      Someone would need to test that.
> Unifying all the timeout handling is definitely something that should be
> looked at.    Http does it's own thing.   JMS does its own thing.   There is
> the stuff in ClientImpl that may interfere with the JMS stuff.   Local doesn't
> do anything (bug is affected by the stuff in ClientImpl).
> Dan
> On Mon May 4 2009 3:31:19 pm conficio wrote:
> > I have a CXF Spring configuration that uses local transport for Unit
> > Testing.
> >
> > However, when I try to debug this in Eclipse I get connection timeouts in
> > about 60s. The only documentation of timeouts I can find is on HTTP
> > connections.
> >
> > What can I do to eliminate (or set to indefinite) the local timeout?
> >
> > K<o>
> ... [show rest of quote]
> -- 
> Daniel Kulp
> dkulp@...
> http://www.dankulp.com/blog
> ----
> As neither svn checkout, not mvn eclipse:eclipse or mvn -Psetup.eclipse as described http://cxf.apache.org/setting-up-eclipse.html does work , I was unable to even take a stab at producing a patch. Sorry I have to leave ti to the experts with a working environment. The mind was willing but the obstacles seem to high ;-)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira