On Fri, 2012-11-09 at 07:12 -0800, rogerdpack wrote: > I noticed that this page: > http://activemq.apache.org/consumer-dispatch-async.html > suggests the following option: "?consumer.dispatchAsync=false" > > which seems to throw (for me) this exception: > Caused by: java.lang.IllegalArgumentException: Invalid connect parameters: > {consumer.dispatchAsync=false} > > maybe the documentation should show > "?jms.dispatchAsync=false" which seems to work better?
Are you setting the consumer.dispatchAsnyc on the destination used to create the consumer, or on the connection uri? If its on the connection uri then the jms.dispatchAsync option would be right but on the destination level then I'd think that the consumer.dispatchAsync is the right one. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/wrong-setting-in-the-docu-tp4659114.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- Tim Bish Sr Software Engineer | RedHat Inc. tim.b...@redhat.com | www.fusesource.com | www.redhat.com skype: tabish121 | twitter: @tabish121 blog: http://timbish.blogspot.com/
