I am trying to use latest release of activemq 5.9.1 with replicated leveldb
setup. I keep seeing following wrning in logs.
2014-04-29 14:43:52,515 | WARN |
org.apache.activemq.broker.region.cursors.QueueStorePrefetch@716c5c8d:JMSHealthCheckDestination,batchResetNeeded=false,storeHasMessages=true,
Hi all
Who know why there is not support amqPersistenceAdapter in ActiveMQ 5.9
anymore ?
I configure the AMQ DB in ActiveMQ 5.9 , got the following error:
ERROR: java.lang.RuntimeException: Failed to execute start task. Reason:
org.springframework.beans.factory.xml.XmlBeanDefinitionSto
have you looked at startupMaxReconnectAttempts and maxReconnectAttempts.
On Tue, Apr 29, 2014 at 7:23 AM, Gary Tully wrote:
> there is currently no way to say retryCurrent X times before trying an
> alternative url in the list and url must be unique so
> there is no way to hack in duplicates.
>
On 04/28/2014 05:34 PM, karcel wrote:
Hi!
I am quite new in here and i got problem connecting to localhost while using
mqtt.
With usingn defaults:
private static String url = ActiveMQConnection.DEFAULT_BROKER_URL;
ConnectionFactory connectionFactory =new
ActiveMQConnectionFacto
Hi!
I am quite new in here and i got problem connecting to localhost while using
mqtt.
With usingn defaults:
private static String url = ActiveMQConnection.DEFAULT_BROKER_URL;
ConnectionFactory connectionFactory =new
ActiveMQConnectionFactory(url);
Connection connection = c
there is currently no way to say retryCurrent X times before trying an
alternative url in the list and url must be unique so
there is no way to hack in duplicates.
maybe create a jira to track the enhancement to allow a retryCount on
the current url before moving on through the list.
On 24 April 2
tabish...@gmail.com wrote
> You have two options
>
> 1. Change the source locally to what you want and build your own client
> libraries.
> 2. Submit a patch to a Jira ticket that allows setting the value while
> keeping the current setting as the default. The patch should provide a
> means of
