Greetings, Based on Willem's response in http://www.nabble.com/forum/ViewPost.jtp?post=19100138&framed=y, it appears that CXF's JMS transport conduit.handleResponse() will block the thread when it waits for the reply. Is this indeed the case as well for the SMX-CXF-BC provider's use of CXF's JMS transport?
If so, should I open a JIRA with CXF and/or SMX-CXF-BC to address this scalability problem? I believe the new SMX-JMS endpoints use Spring JMS templates to get around this problem and I think the old SMX-JMS endpoint used a store/storeFactory. How would it make best sense to address this issue with CXF/SMX-CXF-BC? - Ron -- View this message in context: http://www.nabble.com/Does-SMX-CXF-BC-provider-w-JMS-transport-block-thread-waiting-for-a-reply--tp19102173p19102173.html Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
