Because you are basically mixing two different approaches where clients running
on the same JVM take the advantage of connecting to local brokers and remote
clients connect to the broker using the regular TCP approach.
There are additional references available here:
http://activemq.apache.org/c
On Sat, Oct 1, 2011 at 12:06 AM, Marcelo Jabali wrote:
> Mohit,
>
> ActiveMQ has several transport protocols available (connection URLs for a
> client to connect to a broker).
> TCP - is used when clients connect to the broker using a TCP socket. VM - is
> used when you are embedding the broker
Mohit,
ActiveMQ has several transport protocols available (connection URLs for a
client to connect to a broker).
TCP - is used when clients connect to the broker using a TCP socket. VM - is
used when you are embedding the broker in your app (client and broker running
on the same JVM) and you wa
On Wed, Sep 28, 2011 at 3:33 PM, Timothy Bish wrote:
> On Wed, 2011-09-28 at 14:05 -0700, Mohit Anchlia wrote:
>> I have this config. Trying to understand few things:
>>
>> 1. what's the different between uri="tcp://localhost:0" and
>> brokerURL="vm://localhost" ?
>> 2. In point 1 why are both not
On Wed, 2011-09-28 at 14:05 -0700, Mohit Anchlia wrote:
> I have this config. Trying to understand few things:
>
> 1. what's the different between uri="tcp://localhost:0" and
> brokerURL="vm://localhost" ?
> 2. In point 1 why are both not tcp?
> 3. what is :0? That doesn't look like a port to me.
