[
https://issues.apache.org/activemq/browse/SM-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved SM-1520.
---------------------------------
Assignee: Guillaume Nodet
Fix Version/s: 3.3
Resolution: Fixed
Sending
src/main/java/org/apache/servicemix/jms/endpoints/JmsProviderEndpoint.java
Sending
src/test/java/org/apache/servicemix/jms/JmsProviderEndpointTest.java
Transmitting file data ..
Committed revision 689094.
> SMX-JMX in-out provider should asynchronously handle response messages
> ----------------------------------------------------------------------
>
> Key: SM-1520
> URL: https://issues.apache.org/activemq/browse/SM-1520
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-jms
> Affects Versions: 3.2.2
> Reporter: Ron Gavlin
> Assignee: Guillaume Nodet
> Fix For: 3.3
>
>
> The new smx-jms provider endpoint appears to synchronously wait to receive a
> 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).
> Also see nabble
> (http://www.nabble.com/New-smx-jms-provider-scalability-handling-in-out-MEP-td19129424ef12049.html)
>
> Instead, the provider should probably use a Spring MessageListenerContainer
> to asynchronously handle the response messages. This is a more scalable
> solution, similar to what was provided with the old smx-jms provider endpoint.
> - Ron
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
