I tried this out, it does appear to solve my problem.Thanks!
Can we get it added to the 5.0 release?
Jason
hbruch wrote:
>
> I had problems as well using failover with maxRetryAttempts and
> PooledConnections.
> Might there be a call missing in FailoverTransport to the
> transportListen
I had problems as well using failover with maxRetryAttempts and
PooledConnections.
Might there be a call missing in FailoverTransport to the transportListener
indicating a finally failed connection?
Find attached a patch I applied successfully to AMQ-4.1.1. (
http://www.nabble.com/file/p14181174/F
On 27/11/2007, Jason Rosenberg <[EMAIL PROTECTED]> wrote:
> James,
>
> In this case, I am creating a connection for the purspose of sending a
> message (so not a message listener). I am using the Spring JmsOperations
> template, and just injecting the connectionFactory property for the
> jmsOpera
James,
In this case, I am creating a connection for the purspose of sending a
message (so not a message listener). I am using the Spring JmsOperations
template, and just injecting the connectionFactory property for the
jmsOperations object on initialization.
The connectionFactory is org.jencks
On 26/11/2007, Jason Rosenberg <[EMAIL PROTECTED]> wrote:
>
> I'm curious whether you've found a solution to this. I've seen also that if
> you use the maxReconnectAttempts, and it fails to reconnect, then the
> connection cannot be reliably recovered.
If a connection fails to reconnect it must b
I'm curious whether you've found a solution to this. I've seen also that if
you use the maxReconnectAttempts, and it fails to reconnect, then the
connection cannot be reliably recovered.
I've tried it with the Jencks AMQPool for my connection pooling, as well as
the standard ActiveMQ PooledConne
I have a queueSession that is a singleton for my application on server A.
This queueSession is set at startup. When I start up my application,
activemq is up : my application can send messages. I stop activemq : the
messages are dropped. But when I restart activemq, my application can't send
messa
Yep, that's the normal behavior.
The A servers are probably failing to connect before the B brokers are
started. With the parameters you set, and starting A servers before B
brokers, it's bound to fail...
Try increasing maxReconnectAttempts and maxReconnectDelay parameters,
so there's enoug
OK, it was my mistake, i set a boolean to late...
Now, I have the following configuration :
failover://(tcp://B1:61616,tcp://B2:62626)?maxReconnectAttempts=1&maxReconnectDelay=100
But when I restart my activemq server, my A servers cannot reconnect to it.
When I send a message, I have : javax.jm
I set the maxReconnectAttempts to 1 and it is trying to reconnect endlessly.
And it can't connect to the B servers, even if they are up.
Eduardo Corral wrote:
>
> Hi Delphine
>
> Have you checked the log files? Maybe the clients (A1, A2,...) do follow
> the timeout parameter, but they are try
Hi Delphine
Have you checked the log files? Maybe the clients (A1, A2,...) do follow
the timeout parameter, but they are trying to reconnect endlessly...
http://activemq.apache.org/failover-transport-reference.html
With failover, you may also configure how long between retries and how
many o
11 matches
Mail list logo
