[ https://issues.apache.org/activemq/browse/AMQ-770?page=all ]
james strachan resolved AMQ-770.
--------------------------------
Fix Version/s: 4.1
Resolution: Fixed
This was a documentation error. We default to false to minimise the number of
threads used by default.
http://activemq.org/site/destination-options.html
It would be nice to be able to overload things like this on the broker side
maybe
> consumer.dispatchAsync defaults to false
> ----------------------------------------
>
> Key: AMQ-770
> URL: https://issues.apache.org/activemq/browse/AMQ-770
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMS client
> Affects Versions: 4.0, 4.0.1
> Reporter: Kevin Yaussy
> Priority: Minor
> Fix For: 4.1
>
>
> Seems like there was a change between 4.0-RC3 and incubator-4.0(.1) with
> regards to the default value for the destination option
> "consumer.dispatchAsync". According to the web documentation for destination
> options, as well as behavior in RC3, the default is true. However, it looks
> like incubator-4.0(.1) defaults to false. I have to explicitly give the
> consumer.dispatchAsync=true for a destination option, in order to get async
> dispatch in the Broker.
> Is this a code bug, or documentation bug?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
