You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Rob Davies (JIRA)" <ji...@apache.org> on 2008/04/07 20:16:32 UTC

[jira] Created: (AMQ-1646) Chande dispatchAsync = true for clients by default

Chande dispatchAsync = true for clients by default
--------------------------------------------------

                 Key: AMQ-1646
                 URL: https://issues.apache.org/activemq/browse/AMQ-1646
             Project: ActiveMQ
          Issue Type: Improvement
          Components: JMS client
    Affects Versions: 5.0.0
            Reporter: Rob Davies
            Assignee: Rob Davies
             Fix For: 5.1.0


By default, non-persistent clients (topics) will be dispatched messages from the broker by the same thread that received them from the producer. This means that a slow consumer will slow the overall
throughput for any clients receiving messages from that producer. By having dispatchAsync=true as the default, consumers will be decoupled from the producer.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (AMQ-1646) Change dispatchAsync = true for clients by default

Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.

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

Jim Gomes updated AMQ-1646:
---------------------------

    Summary: Change dispatchAsync = true for clients by default  (was: Chande dispatchAsync = true for clients by default)

> Change dispatchAsync = true for clients by default
> --------------------------------------------------
>
>                 Key: AMQ-1646
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1646
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: JMS client
>    Affects Versions: 5.0.0
>            Reporter: Rob Davies
>            Assignee: Rob Davies
>             Fix For: 5.1.0
>
>
> By default, non-persistent clients (topics) will be dispatched messages from the broker by the same thread that received them from the producer. This means that a slow consumer will slow the overall
> throughput for any clients receiving messages from that producer. By having dispatchAsync=true as the default, consumers will be decoupled from the producer.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (AMQ-1646) Chande dispatchAsync = true for clients by default

Posted by "Rob Davies (JIRA)" <ji...@apache.org>.

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

Rob Davies resolved AMQ-1646.
-----------------------------

    Resolution: Fixed

Fixed by SVN revision 645999

> Chande dispatchAsync = true for clients by default
> --------------------------------------------------
>
>                 Key: AMQ-1646
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1646
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: JMS client
>    Affects Versions: 5.0.0
>            Reporter: Rob Davies
>            Assignee: Rob Davies
>             Fix For: 5.1.0
>
>
> By default, non-persistent clients (topics) will be dispatched messages from the broker by the same thread that received them from the producer. This means that a slow consumer will slow the overall
> throughput for any clients receiving messages from that producer. By having dispatchAsync=true as the default, consumers will be decoupled from the producer.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.