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
