Thanks for your response ceposta.yes i am loading broker in the same JVM.Is
any problem in that?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Problem-in-VM-broker-url-along-with-simpleAuthenticationPlugin-in-activemq-tp4668639p4668682.html
Sent from the ActiveMQ -
Hi,
When can we expect the next ActiveMQ version to be released. We were going
to upgrade to the latest version but can hold if a new version is coming up
shortly. AMQ Devs ??
Thanks,
Bhanu
--
View this message in context:
It was an effort to increase the write throughput, but for kahadb the
bottleneck is the index so any gain/loss for different workloads was
over shadowed.
For the moment, stick with the defaults. The logging may help identify
the best value for journalMaxWriteBatchSize.
On 27 June 2013 18:55,
Hi Chris,
you can take this red hat release that contains the fix
http://repo.fusesource.com/nexus/content/groups/public/org/apache/activemq/activemq-rar/5.8.0.redhat-60024/
Hopefully that can get you through while waiting for 5.9
Regards
--
Dejan Bosanac
--
Red Hat, Inc.
link to the distros -
http://repo.fusesource.com/nexus/content/groups/public/org/apache/activemq/apache-activemq/5.8.0.redhat-60024/
On 28 June 2013 13:29, Dejan Bosanac de...@nighttale.net wrote:
Hi Chris,
you can take this red hat release that contains the fix
not sure if the prefetch matches those of the networkConnectors, seems
to be 1000(default) vs 15000 so it may be a connection
temp advisory consumer. Can be disabled with connection url param
watchTopicAdvisories=false
If you can find the consumer
ID:mco-broker8-57609-1372346502469-88:1:1:1 via
Thanks for the feedback!
On Fri, Jun 28, 2013 at 8:27 AM, Gary Tully gary.tu...@gmail.com wrote:
It was an effort to increase the write throughput, but for kahadb the
bottleneck is the index so any gain/loss for different workloads was
over shadowed.
For the moment, stick with the defaults.
Greetings!
I want ActiveMQ to automatically cleanup (unsubscribe) idle subscribers who
haven't connected in, say, 3 days. I couldn't find this in the
documentation. Is this possible? And if so, what configuration option is
it?
Mark
--
View this message in context:
gcInactiveDestinations is defined as delete inactive destinations that are
empty. An empty destination is not the only criteria under which I want a
destination to be deleted.
Is there a setting, or combination of settings, that will automatically
delete a destination that's not empty but has not
