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 lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <19828777.post@talk.nabble.com>
Date: Sun, 5 Oct 2008 13:20:45 -0700 (PDT)
From: akkij <akash.jain@coreobjects.com>
To: users@activemq.apache.org
Subject: Re: ActiveMQ deployment options
In-Reply-To: <7b3355cb0810051313k4564b328hd9feae9cf9c051a4@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <19828552.post@talk.nabble.com>
 <7b3355cb0810051313k4564b328hd9feae9cf9c051a4@mail.gmail.com>


Thanks Bruce for the reply.

Does it mean that ActiveMQ embedded within tomcat gives better performance
as there is no network call involved?

Akash


bsnyder wrote:
> 
> On Sun, Oct 5, 2008 at 2:00 PM, akkij <akash.jain@coreobjects.com> wrote:
>>
>> Hi,
>>
>> We have decided to use ActiveMQ for asynchronous messaging involved in
>> one
>> of our projects. I have been going through various documentation related
>> to
>> ActiveMQ; however i am looking for a specific information which
>> unfortunately i couldn't get.
>>
>> If i am not mistaken then ActiveMQ can be intalled as a standalone
>> process
>> as well as embedded within tomcat server. If this is correct then i would
>> like to know which of these 2 options is better and why? What happens to
>> the
>> Queue and Messages in case if ActiveMQ is embedded within tomcat and the
>> tomcat instance goes down?
> 
> ActiveMQ provides a few different deployment options, two of which are
> stand alone as its own process and embedded in another process such as
> Tomcat. Neither one is inherently better than the other, it really
> comes down to the advantages and disadvantages of each that should be
> compared for a given situation. Deploying ActiveMQ stand alone means
> that it's not dependent upon other processes. Embedding ActiveMQ
> inside another process means if that process goes down, so does
> ActiveMQ. However, when embedding ActiveMQ in another Java process,
> the vm:// protocol can be used to connect to the broker using local
> calls without using the network stack. Whereas connecting to ActiveMQ
> running stand alone can only be achieved using remote protocols which
> involves TCP sockets.
> 
> Bruce
> -- 
> perl -e 'print
> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
> 
> Apache ActiveMQ - http://activemq.org/
> Apache Camel - http://activemq.org/camel/
> Apache ServiceMix - http://servicemix.org/
> 
> Blog: http://bruceblog.org/
> 
> 

-- 
View this message in context: http://www.nabble.com/ActiveMQ-deployment-options-tp19828552p19828777.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.