Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of mjabali@fusesource.com
 designates 74.125.245.90 as permitted sender)
From: Marcelo Jabali <mjabali@fusesource.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-12--106112837
Subject: Re: Understanding basic config
Date: Sat, 1 Oct 2011 14:11:43 -0700
In-Reply-To: 
 <CAOT3TWqex+KKVHxRJWfqBw78G8RK7PYSbTWqssVeXOKsn0W1XQ@mail.gmail.com>
To: users@activemq.apache.org
References: 
 <CAOT3TWqQD3QHEuQz_d_ydEdmpVN4xE6RRtPzaCj_NHW5fWHsYw@mail.gmail.com>
 <1317249209.2856.11.camel@OfficePC>
 <CAOT3TWqibGMCsR6c57+VOA8CU0gcjbtXjxv_UT_r==q2+K4dtg@mail.gmail.com>
 <9FB9E2AC-B626-4876-9CFF-FF9EB6D22850@fusesource.com>
 <CAOT3TWqex+KKVHxRJWfqBw78G8RK7PYSbTWqssVeXOKsn0W1XQ@mail.gmail.com>
Message-Id: <7F95A58B-7DC2-4D96-A03F-E9D32C226023@fusesource.com>

--Apple-Mail-12--106112837
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

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/configuring-transports.html


On Oct 1, 2011, at 10:31 AM, Mohit Anchlia wrote:

> On Sat, Oct 1, 2011 at 12:06 AM, Marcelo Jabali =
<mjabali@fusesource.com> wrote:
>> Mohit,
>>=20
>> 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 want to take the performance =
benefits of connecting the clients to the broker without hitting the =
network layer. Everything goes through in-memory buffers.
>>=20
>> Hope this helps,
>=20
> That I understand but still not clear about why broker and the factor
> are different? Why would broker listen on tcp if client is using vm
> call?
>=20
> <amq:broker id=3D"BridgeBroker" useJmx=3D"true" persistent=3D"false">
>=20
>   <amq:transportConnectors>
>     <amq:transportConnector uri=3D"tcp://localhost:0" />
>   </amq:transportConnectors>
> </amq:broker>
>=20
>=20
> <!-- JMS ConnectionFactory to use, configuring the embedded broker
> using XML -->
>=20
> <amq:connectionFactory id=3D"BridgeJmsFactory" =
brokerURL=3D"vm://bridgehost"/>
>=20
>>=20
>> -Marcelo
>>=20
>>=20
>> On Sep 28, 2011, at 4:18 PM, Mohit Anchlia wrote:
>>=20
>>> On Wed, Sep 28, 2011 at 3:33 PM, Timothy Bish <tabish121@gmail.com> =
wrote:
>>>> On Wed, 2011-09-28 at 14:05 -0700, Mohit Anchlia wrote:
>>>>> I have this config. Trying to understand few things:
>>>>>=20
>>>>> 1. what's the different between uri=3D"tcp://localhost:0" and
>>>>> brokerURL=3D"vm://localhost" ?
>>>>> 2. In point 1 why are both not tcp?
>>>>> 3. what is :0? That doesn't look like a port to me. Is this =
specifial
>>>>> for embedded broker?
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>  <amq:broker useJmx=3D"false" persistent=3D"false">
>>>>>     <amq:transportConnectors>
>>>>>       <amq:transportConnector uri=3D"tcp://localhost:0" />
>>>>>     </amq:transportConnectors>
>>>>>   </amq:broker>
>>>>>=20
>>>>>    <!--  ActiveMQ destinations to use  -->
>>>>>   <amq:queue id=3D"destination"
>>>>> physicalName=3D"org.apache.activemq.spring.Test.spring.embedded"/>
>>>>>=20
>>>>>   <!-- JMS ConnectionFactory to use, configuring the embedded =
broker
>>>>> using XML -->
>>>>>   <amq:connectionFactory id=3D"jmsFactory" =
brokerURL=3D"vm://localhost"/>
>>>>=20
>>>> Have a look at the Version 5 Transports page for info on the =
various
>>>> transports.
>>>> http://activemq.apache.org/configuring-version-5-transports.html
>>>>=20
>>>> For the TCP transport setting the port to zero means that you want =
the
>>>> broker to pick an open TCP port.  Normally you wouldn't do this in =
the
>>>> configuration since will change every time you start the broker, =
this is
>>>> more useful for unit tests where you want to ensure you get an open
>>>> port.
>>>>=20
>>>>=20
>>>=20
>>> I couldn't get answer to my point 1 and 2
>>>=20
>>> 1. what's the different between uri=3D"tcp://localhost:0" and
>>> brokerURL=3D"vm://localhost" ?
>>>=20
>>>  <amq:broker id=3D"BridgeBroker" useJmx=3D"true" persistent=3D"false">=

>>>    <amq:transportConnectors>
>>>      <amq:transportConnector uri=3D"tcp://localhost:0" />
>>>    </amq:transportConnectors>
>>>  </amq:broker>
>>>=20
>>>  <!-- JMS ConnectionFactory to use, configuring the embedded broker
>>> using XML -->
>>>  <amq:connectionFactory id=3D"BridgeJmsFactory" =
brokerURL=3D"vm://bridgehost"/>
>>>=20
>>> 2. In point 1 why are both not tcp?
>>>=20
>>> 3. And in point 1 how is broker getting associated with the
>>> connectionfactory since url is different?
>>>=20
>>>=20
>>>> Regards
>>>>=20
>>>>=20
>>>>=20
>>>> --
>>>> Tim Bish
>>>> ------------
>>>> FuseSource
>>>> Email: tim.bish@fusesource.com
>>>> Web: http://fusesource.com
>>>> Twitter: tabish121
>>>> Blog: http://timbish.blogspot.com/
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20


--Apple-Mail-12--106112837--