Re: Binding Queues with Topics

2013-05-02 Thread loki12
Thanks a lot Christian this does look like a viable solution. I think 'Using Filtered destination' is the key here. I want to confirm one thing here that is if we publish messages with multiple filters to the topic say "odd = 'yes'" and "i = 5" but we'll only have one filteredDestination as below

Re: AMQ failover using different PCs?

2013-05-02 Thread Johan Edstrom
It is one of the better options, otherwise you are stuck with an RDMBS or a clustering filesystem. LevelDB in very new development offer some new cool stuff. On May 2, 2013, at 10:59 AM, Killhoven wrote: > Thanks! > > This option is definitely doable, but not the best solution. Is there any >

Re: AMQ failover using different PCs?

2013-05-02 Thread Killhoven
Thanks! This option is definitely doable, but not the best solution. Is there any other way to set up two stand-alone PC-s with AMQ, a master and slave ? -- View this message in context: http://activemq.2283324.n4.nabble.com/AMQ-failover-using-different-PCs-tp4666568p4666591.html Sent from

Re: AMQ failover using different PCs?

2013-05-02 Thread Christian Posta
Yep, you can do so with a shared disk so that master and slave look at the same persistent store. When master goes down, slave can take over right where master left off. Take a look here for details: http://activemq.apache.org/shared-file-system-master-slave.html On Thu, May 2, 2013 at 5:18 AM,

Re: Binding Queues with Topics

2013-05-02 Thread Christian Posta
check out virtual topics wiki and the section on filtered composite destinations: http://activemq.apache.org/virtual-destinations.html On Thu, May 2, 2013 at 6:26 AM, loki12 wrote: > Is there a way to bind the queues with Topics based on a property in > message > header to filter the messages I

RE: Durable Topic, only most-recent message needed

2013-05-02 Thread Michael Black
Sound to me like you want a database and not ActiveMq. Producer inserts a record and deletes all previous (in that order in 1 transaction with rollback to assure that clients can always retrieve a record). Use a date/time for the key. Clients retrieve the last key in the table. #1 Clients alway

AMQ failover using different PCs?

2013-05-02 Thread Killhoven
Hi! Is it possible to set up AMQ failover master-slave solution so, that master is in one PC and slave is on other PC? So if something happens with the PC where master is running, secondary is not affected and can take over. If yes, how should I configure? Thanks in advance. -- View this mes

Binding Queues with Topics

2013-05-02 Thread loki12
Is there a way to bind the queues with Topics based on a property in message header to filter the messages I need to get. For example: 1. I have two topics named request and response. 2. I'm getting messages to topic request with a header property with destinations as X and Y 3. I need to bind re

Re: Slow Failover

2013-05-02 Thread thomas.r.parkinson
Creating two producers using Spring JMS template and two consumers using spring DefaultMessageListenerContainer. Using a ActiveMQConnectionFactory for both. When i pull the network cable on broker 4 i see an exception in the jms template about 30 seconds after then 30 seconds after that i see Fai

Re: Slow Failover

2013-05-02 Thread Gary Tully
on your clients, enable trace level logging for : org.apache.activemq.transport.failover.FailoverTransport that will help you see what is going on under the hood till the reconnect occurs. There could be some dns/ip matching issues between the client and the brokers. post the logging output if yo

Re: Durable Topic, only most-recent message needed

2013-05-02 Thread Yin Wang
The non-durable retroactive consumer of Topic will do the trick. http://activemq.apache.org/retroactive-consumer.html Only one condition is not satisfied,messages can not survive from the restart of the broker. 2013/5/2 Andrea Arcuri > Hi, > I am new to ActiveMQ. Reading documentation and pla

Re: Loads of TIME_WAIT connections

2013-05-02 Thread lacigas
You are right, the problem is caused by the client. The expiry timeout for the PooledConnectionFactory was set to 1ms by default, so every connection was going to TIME_WAIT state after 1ms if not used. I have increased this numer and now I have a nice low number of TIME_WAIT connections. thanks L

Durable Topic, only most-recent message needed

2013-05-02 Thread Andrea Arcuri
Hi, I am new to ActiveMQ. Reading documentation and playing with examples. But there is a key scenario I need to implement, but not sure if ActiveMQ can support it, and, if it does, how. - Client publishes topic to broker - Only most recent message on topic is needed - Messages can be very large