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> -- Daniel Kulp [email protected] http://www.dankulp.com/blog
