Thanks Guillaume!

However, I'd like to comment on the fact that ActiveMQ is in fact clustered
by default. The "traditional" way of installing servers is that they are
stand-alone, but the ESB is a bit different of course. I'm not saying it is
wrong to have ActiveMQ clustered by default, a good solution would be
comments on how to turn it off in the activemq.xml for instance. ;)

Kind regards,
/Eyji


gnodet wrote:
> 
> You need to remove the <networkConnector/> tag
> and also the discoveryUri attribute on the transportConnector.
> That way, the ActiveMQ instances won't be clustered.
> 
> On 11/16/06, Eyji <[EMAIL PROTECTED]> wrote:
>>
>> We have installed a SM development and test environments on the same
>> physical
>> machine as single instances, separated by port number entries of course.
>> The
>> problem we have now is that when we send JMS messages to, say, the test
>> instance, the message is received by the development instance and vice
>> versa
>> as if in a clustered environment.
>> Among other things, I tried to comment out the  <networkConnector
>> uri="multicast....> entry in the activemq.xml without success. We use a
>> JCA
>> flow for our messages if that is a helpful hint.
>>
>> Greatful for any help in this matter,
>> /Eyji
>> --
>> View this message in context:
>> http://www.nabble.com/Involuntary-distribution-of-messages-tf2641701s12049.html#a7373986
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
>>
> 
> 
> -- 
> Cheers,
> Guillaume Nodet
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Involuntary-distribution-of-messages-tf2641701s12049.html#a7375223
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to