Greetings, After taking a brief look at the implementation code for smx-jms, it appears the old smx-jms provider endpoint handles async IN-OUT MEPs via an async callback mechanism which seems quite scalable (see method onMessage() in http://fisheye6.atlassian.com/browse/~raw,r=602826/servicemix/smx3/trunk/deployables/bindingcomponents/servicemix-jms/src/main/java/org/apache/servicemix/jms/multiplexing/MultiplexingProviderProcessor.java).
OTOH, the new smx-jms provider endpoint appears to synchronously wait to receive the response message from the reply-to queue (see method processInOutInSession() in http://fisheye6.atlassian.com/browse/~raw,r=602826/servicemix/smx3/trunk/deployables/bindingcomponents/servicemix-jms/src/main/java/org/apache/servicemix/jms/endpoints/JmsProviderEndpoint.java). Although the new Spring-based provider endpoints provide many new features, as far as scalability is concerned, this seems to be a major step backwards. Should I open a JIRA to enhance the new smx-jms provider endpoints with an async callback mechanism to improve scalability? - Ron -- View this message in context: http://www.nabble.com/New-smx-jms-provider-scalability-handling-in-out-MEP-tp19129424p19129424.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
