Hi Marnie,

Sorry I got you wrong ! We are using NON_PERSISTENT !

Lahiru

On Fri, Jun 11, 2010 at 2:10 AM, Marnie McCormack <
marnie.mccormack@googlemail.com> wrote:

> Yes, if you google JMS delivery mode you'll see what I mean - persistent is
> the default for send() on a MessageProducer.
>
> Marnie
>
> On Thu, Jun 10, 2010 at 6:01 PM, Lahiru Gunathilake <glahiru@gmail.com
> >wrote:
>
> > On Thu, Jun 10, 2010 at 9:53 PM, Marnie McCormack <
> > marnie.mccormack@googlemail.com> wrote:
> >
> > > Whats your message delivery mode ?
> > >
> > It's JMS !
> >
> >
> > Thanks
> > Lahiru
> >
> > >
> > > Marnie
> > >
> > > On Thu, Jun 10, 2010 at 5:12 PM, Lahiru Gunathilake <glahiru@gmail.com
> > > >wrote:
> > >
> > > > Hi Marnie,
> > > >
> > > > Thanks for the reply, what do you mean by persistent messaging ? from
> > our
> > > > ESB side we do not have failover configuration but we can always
> > > configure
> > > > a
> > > > failover scenario to piont to another qpid instance and from the
> other
> > > esb
> > > > we can register all the qpid instances as listeners so those guys
> will
> > > pick
> > > > messages whenever message comes to qpid failover instances.
> > > >
> > > > On Thu, Jun 10, 2010 at 9:20 PM, Marnie McCormack <
> > > > marnie.mccormack@googlemail.com> wrote:
> > > >
> > > > > Hi Lahiru,
> > > > >
> > > > > Are you using persistent messaging and also do you use failover on
> > > client
> > > > > connections ?
> > > > >
> > > > > There's currently no clustering support, but I can give you some
> > ideas
> > > > > about
> > > > > using multiple brokers and depolyment models we've used.
> > > > >
> > > > can you please give a little explanation on this approach and that
> will
> > > be
> > > > really useful for me !
> > > >
> > > >
> > > > Thanks in advance
> > > > Lahiru
> > > >
> > > > >
> > > > > Regards,
> > > > > Marnie
> > > > >
> > > > > On Thu, Jun 10, 2010 at 2:29 PM, Lahiru Gunathilake <
> > glahiru@gmail.com
> > > > > >wrote:
> > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > I am using Qpid as the message storage between two ESB instances
> > and
> > > > one
> > > > > > ESB
> > > > > > is sending messages to Qpid and other guy is picking those
> messages
> > > > from
> > > > > > Qpid since the first ESB is not allowed to create a connection in
> > to
> > > > the
> > > > > > Zone where second ESB is running. So in this scenario we are
> having
> > a
> > > > > > single
> > > > > > point of failure in the Qpid instance running in between and I am
> > > using
> > > > > > Qpid
> > > > > > java broker.
> > > > > >
> > > > > > Is there solution with Qpid Java broker for this problem, like
> > > > clustering
> > > > > > the Qpid or what type of federation support Qpid Java broker is
> > > > providing
> > > > > ?
> > > > > >
> > > > > > Can somebody please point me to a document if you are already
> > > > supporting
> > > > > > this with Java broker ?
> > > > > >
> > > > > > Regards
> > > > > > Lahiru
> > > > > >
> > > > > > --
> > > > > > Apache Qpid, Worlds dominant messaging middleware..!!!
> > > > > >
> > > > > > Senior Software Engineer
> > > > > > WSO2 Inc
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > >  Apache Qpid, Worlds dominant messaging middleware..!!!
> > > >
> > > > Senior Software Engineer
> > > > WSO2 Inc
> > > >
> > >
> >
> >
> >
> > --
> >  Apache Qpid, Worlds dominant messaging middleware..!!!
> >
> > Senior Software Engineer
> > WSO2 Inc
> >
>



-- 
Apache Qpid, Worlds dominant messaging middleware..!!!

Senior Software Engineer
WSO2 Inc