Hi,
We've been using Activemq version 4.1.1 for almost a year, over TCP
transport, with journal + mysql DB for persistence.
Recently, we observe in STG env. that some messages fail to be dequeued
properly from some queues, though consumers appear to function normally.
Some of these queues have
irst attempt only. Is it
> reconnecting immediately on the first try?
>
> Use the maxReconnectDelay to specify the delay for succeeding attempts.
> http://activemq.apache.org/failover-transport-reference.html
>
> Regards,
> Adrian Co
>
> Qian Su wrote:
>> Hi,
&
/(tcp://localhost:61616)?maxReconnectAttempts=2&initialReconnectDelay=1
Is this the correct way to set initial reconnect delay?
Thanks,
Qian
On 29/02/2008, Qian Su <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> We are using Activemq version 4.1.1, tcp transport and we'd like t
Hi,
We are using Activemq version 4.1.1, tcp transport and the producers are
configured to connect to a single load balancer that distributes requests to
individual brokers. However, more often than not, we notice symptons where
jms messge queuing requests are not probably load balanced, mainly
Hi,
We are using Activemq version 4.1.1, tcp transport and we'd like the
producer to retry at least once in case of connection timeout to a broker.
The brokers are configured behind a load balancer.
Does Activemq support retries on the producer end?
I am aware of the FailoverTransport and know
topic subscribers. Are you
> using queues by any chance?
>
> On 8/2/07, Qian Su <[EMAIL PROTECTED]> wrote:
>>
>> Hi,
>>
>> We are using ActiveMQ 4.1.1 with journaledJDBCPersistence and our
>> datasource
>> is MySQL 5.0.29. We have verified that mes
Hi,
We are using ActiveMQ 4.1.1 with journaledJDBCPersistence and our datasource
is MySQL 5.0.29. We have verified that messages can be successfully sent and
consumed whether producers and consumers are concurrently available.
However, one thing I noticed is that ACTIVEMQ_ACKS table seems to neve
