Hi Freeman, I'll try explicitly setting the timeout as you suggest.
However, I don't understand how it could be a timeout problem given that the sync case works out of the box without setting these timeout values. My sync and async test cases are identical except that the ME sender uses send vs. sendSync. Would you expect these timeout configurables to be significant in the async case but insignificant in the sync case? - Ron ----- Original Message ---- From: Freeman Fang <[EMAIL PROTECTED]> To: [email protected] Sent: Friday, May 16, 2008 9:56:28 AM Subject: Re: Timeout using cxf-bc provider w/async inout MEP and jms binding Hi Ron, For jms client timeout configuration, you can write a spring bean, let's say jms-client.xml, some thing like <jms:conduit name="{http://cxf.apache.org/jms_endpt}HelloWorldJMSPort.jms-conduit";> ... <jms:clientConfig clientReceiveTimeout="500" messageTimeToLive="500" /> </jms:conduit> then put this file for your cxf provider busCfg attribute, you can specify the timeout as you want, for more details how is the spring file looks like, please refer to [1] [1]http://cwiki.apache.org/CXF20DOC/jms-transport.html Regards Freeman Ron Gavlin wrote: > We have a flow in which we send an asynchronous inout messageExchange to a > cxf-bc provider endpoint whose wsdl is configured with a jms binding. This > flow results in a > > "java.io.IOException: javax.jms.JMSException: JMSClientTransport.receive() > timed out. No message available" > > exception in the cxf-bc provider. If we send the same messageExchange using a > sendSync instead of a send, the flow works perfectly. This seems like a bug > in the cxf-bc provider's jms support. Do you agree? If so, I will open a JIRA. > > Thanks, > > - Ron > > >
