activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hardikphd <>
Subject Re: Connection Factory Problem
Date Tue, 12 Jun 2007 07:29:26 GMT

Hi James,

Actually, I want only one receiver and more than one producer and receiver
will send response back to only one sender and all senders and receiver are
on different machine.

And as I have many senders, I don't want to configure connectionfactory for
each of sender at receiver side and still want to get connection to broker
running on sender's machine and send message it to.

Will setJMSReplyTo work across different tomcats?

James.Strachan wrote:
> On 6/12/07, hardikphd <> wrote:
>> Hi All,
>> I am facing problem in getting connection factory.
>> basically, I have single consumer queue and many server (providers)
>> providing message to same queue, After receiving message from any of
>> server,
>> Consumer has to send back one more message back to same server.
> So you could use the JMSReplyTo header using a temporary queue for the
> destination to use for nodes to reply to (to ensure messages go back
> to the same node)
> However what happens if the server is taken down; what should the
> consumer do (as the temporary queue would no longer exist). You could
> use a real queue per server (and then assume that at some point the
> server will come back and carry on).
> Another approach is to use Message Groups as an alternative to the
> JMSReplyTo (so using the JMSXGroupID to mark a 'conversation'); which
> would mean if a server dies, another server would take over for all
> future messages in a specific conversation (or value of JMSXGroupID on
> a message)
>> I am using Tomcat 5.5 and consumer and providers are running on different
>> tomcat (or machine)
>> Now, I dont want to configure Connectionfactory for each server
>> specifying
>> broker uri of server at consumer's server 's xml file.
>> Anyway to achieve this functionality?
> I don't quite understand this part. You typically only need a single
> broker; so just configure the ConenctionFactory's brokerURL to point
> to where your're running the broker. If you don't wanna use that you
> could use multicast discovery to find the broker (though be very
> careful development, testing & production don't accidentally find each
> other!)
> -- 
> James
> -------

View this message in context:
Sent from the ActiveMQ - Dev mailing list archive at

View raw message