Well, my tester has encountered more prioritized message queue test failures
even though she removed those prefetch=0 policies from the activemq.xml
config file, and the failures are resolved if she uses a queue name when
specifying the prioritizedMessages="true" policy, instead of attempting to
use simply ">" for all queues.
Btw, my REST client is very unhappy when I set consumer.prefetchSize=0 in
"webapps/demo/WEB-INF/web.xml" via:
<init-param>
<param-name>destinationOptions</param-name>
<param-value>consumer.prefetchSize=0</param-value>
</init-param>
Is that supported for REST API clients?
-----
Stephen Vincent
--
View this message in context: http://activemq.2283324.n4.nabble.com/Does-the-destination-wildcard-require-at-least-one-character-preceding-it-tp4662468p4662656.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
|