Persistant Publish Subscribe mechanism in Qpid

[Yogesh Rao-2]

Hi

I need to know if a persistent publish subscribe mechanism is
available / possible in Qpid using java and if yes how can i do it ???

It would be great if you direct me to a appropriate link

Thank you for the help

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[hidden email]

[Robert Greig]

2009/10/10 Yogesh Rao <[hidden email]>:

> I need to know if a persistent publish subscribe mechanism is
> available / possible in Qpid using java and if yes how can i do it ???

Yes, this is a standard feature of JMS and Qpid is fully JMS compliant.

> It would be great if you direct me to a appropriate link

Take a look at section 5.2.1 on this page:

http://java.sun.com/products/jms/tutorial/1_3_1-fcs/doc/advanced.html

Robert

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[hidden email]

[Yogesh Rao-2]

Thanks robert !!
I was checking the manuals available on qpid site and it only mentions a
JDBC store as part of the message store's available...

How to configure this is not mentioned ...

http://qpid.apache.org/jdbcstore.html

where can i get more info on this ?

Thanks in advance ...




On Sun, Oct 11, 2009 at 12:00 AM, Robert Greig <[hidden email]>wrote:

> 2009/10/10 Yogesh Rao <[hidden email]>:
>
> > I need to know if a persistent publish subscribe mechanism is
> > available / possible in Qpid using java and if yes how can i do it ???
>
> Yes, this is a standard feature of JMS and Qpid is fully JMS compliant.
>
> > It would be great if you direct me to a appropriate link
>
> Take a look at section 5.2.1 on this page:
>
> http://java.sun.com/products/jms/tutorial/1_3_1-fcs/doc/advanced.html
>
> Robert
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:[hidden email]
>
>

[Robert Greig]

2009/10/12 Yogesh Rao <[hidden email]>:
> Thanks robert !!
> I was checking the manuals available on qpid site and it only mentions a
> JDBC store as part of the message store's available...
>
> How to configure this is not mentioned ...
>
> http://qpid.apache.org/jdbcstore.html
>
> where can i get more info on this ?

I am not sure whether that is a recommended option. Certainly I
believe that the Berkeley DB store is more widely used in production
environments. You can get details here:

http://qpid.apache.org/3rd-party-libraries.html

For licencing reasons it is hosted externally from Apache.

I have assumed from the link you provided that you are using the Java broker.

Robert

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[hidden email]

[Martin Ritchie]

2009/10/10 Robert Greig <[hidden email]>:
> 2009/10/10 Yogesh Rao <[hidden email]>:
>
>> I need to know if a persistent publish subscribe mechanism is
>> available / possible in Qpid using java and if yes how can i do it ???
>
> Yes, this is a standard feature of JMS and Qpid is fully JMS compliant.
>
>> It would be great if you direct me to a appropriate link

There is some detail in our FAQ but I've updated our lt to include
links to the Derby Message Store for providing Apache Licensed
persistence and is bundled with the recent releases. The only cavet is
that it has not had as much reported testing.

In summary you just need to ensure you use the DerbyMessageStore
class, as below:
        <virtualhost>
            <name>development</name>
            <development>
                <store>

<class>org.apache.qpid.server.store.DerbyMessageStore</class>

<environment-path>${work}/derbystore/development-store</environment-path>
                </store>
            </development>
        </virtualhost>

Hope that helps

Martin

> Take a look at section 5.2.1 on this page:
>
> http://java.sun.com/products/jms/tutorial/1_3_1-fcs/doc/advanced.html
>
> Robert
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:[hidden email]
>
>

--
Martin Ritchie

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[hidden email]

[Robert Greig]

2009/10/13 Martin Ritchie <[hidden email]>:

> There is some detail in our FAQ but I've updated our lt to include
> links to the Derby Message Store for providing Apache Licensed
> persistence and is bundled with the recent releases. The only cavet is
> that it has not had as much reported testing.

Just to clear for our users - are we recommending the Derby store or
the BDB store for production use?

RG

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[hidden email]

[Marnie McCormack]

My view is that we recommend BDB, simply because we know that it performs
under heavy load. I'm not sure what kind of
robustness/performance/reliability tests have been run on Derby - anyone ?

Marnie

On Tue, Oct 13, 2009 at 9:46 PM, Robert Greig <[hidden email]>wrote:

> 2009/10/13 Martin Ritchie <[hidden email]>:
>
> > There is some detail in our FAQ but I've updated our lt to include
> > links to the Derby Message Store for providing Apache Licensed
> > persistence and is bundled with the recent releases. The only cavet is
> > that it has not had as much reported testing.
>
> Just to clear for our users - are we recommending the Derby store or
> the BDB store for production use?
>
> RG
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:[hidden email]
>
>

[Rob Godfrey]

I would certainly agree that currently we have more experience with the BDB
based store - it also (last time I checked it) gave much better performance
also... so for those two reasons I would currently recommend it over the
Derby store in production use.  The Derby store is probably easier to query
directly and to have a look at the data inside however.

-- Rob



2009/10/14 Marnie McCormack <[hidden email]>

> My view is that we recommend BDB, simply because we know that it performs
> under heavy load. I'm not sure what kind of
> robustness/performance/reliability tests have been run on Derby - anyone ?
>
> Marnie
>
> On Tue, Oct 13, 2009 at 9:46 PM, Robert Greig <[hidden email]
> >wrote:
>
> > 2009/10/13 Martin Ritchie <[hidden email]>:
> >
> > > There is some detail in our FAQ but I've updated our lt to include
> > > links to the Derby Message Store for providing Apache Licensed
> > > persistence and is bundled with the recent releases. The only cavet is
> > > that it has not had as much reported testing.
> >
> > Just to clear for our users - are we recommending the Derby store or
> > the BDB store for production use?
> >
> > RG
> >
> > ---------------------------------------------------------------------
> > Apache Qpid - AMQP Messaging Implementation
> > Project:      http://qpid.apache.org
> > Use/Interact: mailto:[hidden email]
> >
> >
>