Hi Arjen,
ok. glad that you solved this one.
Just as a remark : "reliable" has been replaced with "failover" from
ActiveMQ version 3.x onwards.
Cheers,
Felix
Arjen van der Meijden wrote:
>
> Hi Felix,
>
> I did try 'reliable:tcp://...' but that didn't work, the url wasn't
> accepted. I d
Hi Felix,
I did try 'reliable:tcp://...' but that didn't work, the url wasn't
accepted. I didn't think to use failover on a single connection.
But I did resolve the issue for now by altering the spring-configuration
to only cache connections rather than also cache the entire consumer.
Spring'
Hi Arjen,
did you try to enable failover transport mechanism :
http://activemq.apache.org/failover-transport-reference.html
This will enable the client to reconnect in case of disconnection. the
default transport url you use will NOT automatically reconnect.
Cheers,
Felix
Arjen van der Meijde
Noone with an idea? Do I need to supply more information and/or do more
testing?
Best regards,
Arjen
On 25-9-2009 9:09, Arjen van der Meijden wrote:
Hi List,
I have some topics with very few messages (it can be days or weeks
before a message arrives) on it. The consumers to those topics
di
