Need to see the connection string for the activemq connection factory
called 'remoteactivemq'!
On 17/06/2010 13:10, Łukasz Budnik wrote:
Sure thing:
The route is very simple:
<route>
<from
uri="remoteactivemq:topic:remotetopic?clientId=UniqueIdHere&durableSubscriptionName=AscariCamelRoute&subscriptionDurable=true&cacheLevelName=CACHE_CONSUMER"
/>
<to uri="file:target/messages/remotetopic" />
</route>
remoteacrtivemq is a standalone ActiveMQ.
thanks,
Łukasz
On 17 June 2010 13:49, Adrian Trenaman<[email protected]> wrote:
can you send me your connection string?
On 17/06/2010 12:40, Łukasz Budnik wrote:
Thanks Ade for a hint,
I googled for reconnect string but found nothing. But I found
something similar. When you use topics you can create a durable
client. I did so:
But after restarting ActiveMQ, my route didn't start consuming
messages from my topic. On the ActiveMQ admin console
http://localhost:8161/admin/subscribers.jsp page I saw that connection
ID is set to offline and new messages are all pending.
Client ID Subscription Name Connection ID
Destination
Selector Pending Queue Size
UniqueIdHere AscariCamelRoute OFFLINE remotetopic
43
Has anyone experienced (and solved) this problem?
thanks,
Łukasz
On 17 June 2010 11:42, Adrian Trenaman<[email protected]> wrote:
You need to set your reconnection settings on the ActiveMQ connection
string! AFAIR, Camel doesn't reconnect by default.
Cheers,
Ade.
On 17/06/2010 09:51, Łukasz Budnik wrote:
Hi all,
I'm new to Camel and I'm evaluating it.
I have a simple scenario: I want to consume messages from a remote
Active
MQ:
<route>
<from uri="remoteactivemq:queue:remotequeue" />
<to uri="file:target/messages/remotequeue" />
</route>
Everything works fine until I kill Active MQ. Camel disconnects from
ActiveMQ. When the ActiveMQ is started again, new messages are not
being consumed. Route is a zombie, it is started but not active any
more.
How to solve this problem?
thanks,
Łukasz
