On 10/23/2015 05:09 PM, rth wrote: > So this is a little weird. One of my QA colleagues ran out of memory in a > Java client. She was reading the docs and came across this page > <http://activemq.apache.org/cms/configuring.html> , which she did not > realize is documentation for ActiveMQ-CPP. Even though this was a Java > client, she added this option to her connection string: > > cms.PrefetchPolicy.durableTopicPrefetch=10. > > This is the weird part: that seemed to fix her out-of-memory problem on a > Java client. > > Does that make any sense at all? Do the ActiveMQ-cpp options really work for > Java clients? Or was this some fluke and the test she's running is not as > deterministic in memory consumption as we think? > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Connection-configuration-options-do-cms-options-work-in-Java-tp4703342.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > The java client would not pick this option up, given the cms. prefix. For the java client the option would actually be:
jms.prefetchPolicy.durableTopicPrefetch=10 -- Tim Bish Sr Software Engineer | RedHat Inc. tim.b...@redhat.com | www.redhat.com twitter: @tabish121 blog: http://timbish.blogspot.com/
