You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2008/10/07 09:54:52 UTC

[jira] Updated: (SM-1520) SMX-JMX in-out provider should asynchronously handle response messages

     [ https://issues.apache.org/activemq/browse/SM-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet updated SM-1520:
--------------------------------

    Fix Version/s: servicemix-jms-2008.01

> 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, servicemix-jms-2008.01
>
>
> 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.