You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by jjw tectec <jj...@gmail.com> on 2015/09/03 20:43:41 UTC

How to make Qpid broker persistent?

Hello,

I'm trying to make my qpid broker persistent, but have been getting some
issues.

Below is my cmake output, which indicates Legacystore disabled and
Linearstore enabled. (I do see linearstore.so in the build/src folder by
the way.)
-- Found BerkeleyDB: /usr/lib/x86_64-linux-gnu/libdb_cxx.so
-- Looking for io_queue_init in aio
-- Looking for io_queue_init in aio - found
-- Looking for include file libaio.h
-- Looking for include file libaio.h - found
-- BerkeleyDB for C++ and libaio found, Legacystore support disabled by
default (deprecated, use linearstore instead).
-- Legacystore is excluded from build.
-- Found BerkeleyDB: /usr/lib/x86_64-linux-gnu/libdb_cxx.so
-- BerkeleyDB for C++ and libaio found, Linearstore support enabled.
-- Including BDB from /usr/include/db_cxx.h
-- Building linearstore tests

When starting the broker, using the following command (with an empty
qpidd.conf):
./qpidd -p 5672 --config ../../etc/qpidd.conf --auth no --storage-provider
./linearstore.so

The console output says "no storage provider available". How can I specify
a storage provider here? I thought "--storage-provider ./linearstore.so"
was trying to achieve the purpose. No?

(I'm using proton 0.10 and cpp broker 0.34.)

Thanks

jjw

Re: How to make Qpid broker persistent?

Posted by jjw tectec <jj...@gmail.com>.
Thanks Gordon and Ted.
I got this to work now. :)

On Fri, Sep 4, 2015 at 3:12 AM, Gordon Sim <gs...@redhat.com> wrote:

> On 09/03/2015 09:54 PM, jjw tectec wrote:
>
>> Hi Gordon,
>>
>> Thanks so much for your help. I think I got this to work partially now.
>> The Linear Store inside the broker seems to be working, because I see the
>> below messages:
>> 2015-09-03 15:39:58 [Store] info Linear Store: Most recent persistence id
>> found: 0x0
>> 2015-09-03 15:39:58 [Store] info Linear Store: Recovered exchange
>> "topic.xxx"
>>
>> However, if I create a durable exchange and send durable messages to it,
>> and then shutdown the broker, and restart the broker. The broker did not
>> retain those messages. Please see the commands and queue statistics below.
>> What did I do wrong?
>>
>
> Exchanges don't store messages, they merely route them to any matching
> bound queues. It is queues which store the messages.
>
> So e.g. if you do:
>
> qpid-config -a localhost:5672 --durable add queue my-queue
>
> and then sent the message to that instead of the exchange, you should see
> a message in the queue before and after restart (qpid-stat -q).
>
> If you want to keep the publisher sending to an exchange, you can bind a
> queue to that exchange. This is done automatically if you create a receiver
> from the exchange, but by default the subscription queue would not be
> durable. For a durable subscription you would specify "topic.xxx;
> {link:{name:my-sub,durable:True}}".
>
> ./qpid-config -a localhost:5672 --durable add exchange topic topic.xxx
>> inside the publisher code, I did:
>> Message msg = Message(s);
>> msg.setDurable(1);
>> sender.send(msg);
>> Aggregate Broker Statistics: (BEFORE shutdown)
>>    Statistic                   Messages  Bytes
>>    =============================================
>>    queue-depth                 0         0
>>    total-enqueues              3         627
>>    total-dequeues              3         627
>>    persistent-enqueues         3         627
>>    persistent-dequeues         3         627
>>
>>
>>    Aggregate Broker Statistics: (AFTER shutdown)
>>    Statistic                   Messages  Bytes
>>    =============================================
>>    queue-depth                 0         0
>>    total-enqueues              0         0
>>    total-dequeues              0         0
>>    persistent-enqueues         0         0
>>    persistent-dequeues         0         0
>>
>>   Thanks
>>   jjw
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>

Re: How to make Qpid broker persistent?

Posted by Gordon Sim <gs...@redhat.com>.
On 09/03/2015 09:54 PM, jjw tectec wrote:
> Hi Gordon,
>
> Thanks so much for your help. I think I got this to work partially now.
> The Linear Store inside the broker seems to be working, because I see the
> below messages:
> 2015-09-03 15:39:58 [Store] info Linear Store: Most recent persistence id
> found: 0x0
> 2015-09-03 15:39:58 [Store] info Linear Store: Recovered exchange
> "topic.xxx"
>
> However, if I create a durable exchange and send durable messages to it,
> and then shutdown the broker, and restart the broker. The broker did not
> retain those messages. Please see the commands and queue statistics below.
> What did I do wrong?

Exchanges don't store messages, they merely route them to any matching 
bound queues. It is queues which store the messages.

So e.g. if you do:

qpid-config -a localhost:5672 --durable add queue my-queue

and then sent the message to that instead of the exchange, you should 
see a message in the queue before and after restart (qpid-stat -q).

If you want to keep the publisher sending to an exchange, you can bind a 
queue to that exchange. This is done automatically if you create a 
receiver from the exchange, but by default the subscription queue would 
not be durable. For a durable subscription you would specify "topic.xxx; 
{link:{name:my-sub,durable:True}}".

> ./qpid-config -a localhost:5672 --durable add exchange topic topic.xxx
> inside the publisher code, I did:
> Message msg = Message(s);
> msg.setDurable(1);
> sender.send(msg);
> Aggregate Broker Statistics: (BEFORE shutdown)
>    Statistic                   Messages  Bytes
>    =============================================
>    queue-depth                 0         0
>    total-enqueues              3         627
>    total-dequeues              3         627
>    persistent-enqueues         3         627
>    persistent-dequeues         3         627
>
>
>    Aggregate Broker Statistics: (AFTER shutdown)
>    Statistic                   Messages  Bytes
>    =============================================
>    queue-depth                 0         0
>    total-enqueues              0         0
>    total-dequeues              0         0
>    persistent-enqueues         0         0
>    persistent-dequeues         0         0
>
>   Thanks
>   jjw


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Re: How to make Qpid broker persistent?

Posted by Gordon Sim <gs...@redhat.com>.
On 09/04/2015 06:58 AM, Michael Ivanov wrote:
> You have mentioned that the messages can be both durable and non-durable.
> How this is controlled in proton?

Use pn_message_set_durable() on the messages you send.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Re: How to make Qpid broker persistent?

Posted by Fraser Adams <fr...@blueyonder.co.uk>.
Hey Mikhail,
IIRC the configuration options are a bit limited in that you can't 
configure a queue such that the queue itself survives restarts but 
*force* messages not to be - in other words I think that it will always 
honour the message durability setting, which is I think durable by 
default. So basically you can't do what you want in a *transparent* way.

However if you have control of the message producer and are able to 
request that producers set message durability to false then I think you 
can achieve what you want.

For proton doing

pn_message_set_durable(message, 0);

Should (I think) do the trick (I haven't tried it though).


TBH I think it would be nice to have a bit more control over durability 
options so that queue and message durability could be configured 
separately they are *not* the same thing, if you own the message 
producers you can work around this as above, but if not, or if you have 
lots of producer systems it's a pain 'cause if one of them doesn't set 
message durability to false you can potentially fill stores up 
unexpectedly - or worse.

HTH,
Frase

On 04/09/15 06:58, Michael Ivanov wrote:
> Sorry to intrude into your discussion, but I have related question.
> You have mentioned that the messages can be both durable and non-durable.
> How this is controlled in proton? I need all my durable queues to be
> persistend over qpidd restart but I don't care about messages.
> When I have installed linearstore all my queues were persistent, but
> it seems for these queues all messages went through the disk storage
> which slowed down the operation quite noticeably.
>
> Best regards,


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Re: How to make Qpid broker persistent?

Posted by Michael Ivanov <iv...@logit-ag.de>.
Sorry to intrude into your discussion, but I have related question.
You have mentioned that the messages can be both durable and non-durable.
How this is controlled in proton? I need all my durable queues to be
persistend over qpidd restart but I don't care about messages.
When I have installed linearstore all my queues were persistent, but
it seems for these queues all messages went through the disk storage
which slowed down the operation quite noticeably.

Best regards,
-- 
 \   / |			           |
 (OvO) |  Mikhail Iwanow                   |
 (^^^) |      Voice:   +7 (911) 223-1300   |
  \^/  |      E-mail:  ivans@logit-ag.de   |
  ^ ^  |                                   |

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Re: How to make Qpid broker persistent?

Posted by Ted Ross <tr...@redhat.com>.
Jjw,

The statistics that you are showing are actually consistent and correct. 
  Before shutdown there are 3 enqueues and 3 dequeueus, resulting in 
zero queued messages (the queue-depth).  After restart, the statistics 
show the same expected queue-depth of zero.

Are you consuming the messages and expecting them to still be stored in 
the broker?

-Ted

On 09/03/2015 04:54 PM, jjw tectec wrote:
> Hi Gordon,
>
> Thanks so much for your help. I think I got this to work partially now.
> The Linear Store inside the broker seems to be working, because I see the
> below messages:
> 2015-09-03 15:39:58 [Store] info Linear Store: Most recent persistence id
> found: 0x0
> 2015-09-03 15:39:58 [Store] info Linear Store: Recovered exchange
> "topic.xxx"
>
> However, if I create a durable exchange and send durable messages to it,
> and then shutdown the broker, and restart the broker. The broker did not
> retain those messages. Please see the commands and queue statistics below.
> What did I do wrong?
>
> ./qpid-config -a localhost:5672 --durable add exchange topic topic.xxx
> inside the publisher code, I did:
> Message msg = Message(s);
> msg.setDurable(1);
> sender.send(msg);
> Aggregate Broker Statistics: (BEFORE shutdown)
>    Statistic                   Messages  Bytes
>    =============================================
>    queue-depth                 0         0
>    total-enqueues              3         627
>    total-dequeues              3         627
>    persistent-enqueues         3         627
>    persistent-dequeues         3         627
>
>
>    Aggregate Broker Statistics: (AFTER shutdown)
>    Statistic                   Messages  Bytes
>    =============================================
>    queue-depth                 0         0
>    total-enqueues              0         0
>    total-dequeues              0         0
>    persistent-enqueues         0         0
>    persistent-dequeues         0         0
>
>   Thanks
>   jjw
>
> On Thu, Sep 3, 2015 at 2:29 PM, Gordon Sim <gs...@redhat.com> wrote:
>
>> On 09/03/2015 08:16 PM, jjw tectec wrote:
>>
>>> Thanks for your reply. I had tried many different command options before,
>>> they all had different problems. Below is the output of the execution:
>>>
>>> ./qpidd -p 5672 --auth no --load-module ./linearstore.so
>>>
>>> 2015-09-03 14:12:50 [Broker] notice Broker (pid=6278) start-up
>>> 2015-09-03 14:12:50 [Store] notice Linear Store: Store module initialized;
>>> store-dir=/home/mmos/.qpidd
>>> 2015-09-03 14:12:50 [Store] notice Linear Store: Store module initialized;
>>> store-dir=/home/mmos/.qpidd
>>> 2015-09-03 14:12:50 [Broker] error Multiple store plugins are not
>>> supported
>>> 2015-09-03 14:12:50 [Broker] critical Broker (pid=6278) start-up failed:
>>> Failed to start broker: Multiple store plugins were loaded
>>> (/home/mmos/qpid/qpid-cpp-0.34/src/qpid/broker/Broker.cpp:505)
>>>
>>
>> Ok, so this probably mean you have the store module installed into the
>> default module directory. One option is to just leave out the --load-module
>> ./linearstore.so. The one issue there is you need to make sure the version
>> of the module you load is compatible with the qpidd binary.
>>
>> The other option is to add --no-module-dir i.e.
>>
>> ./qpidd -p 5672 --auth no --no-module-dir --load-module ./linearstore.so
>> --log-enable info+
>>
>> That should at get the module loaded and hopefully the rest of the errors
>> were related to trying to load the module twice.
>>
>> Once the module is loaded, the other point to note is that only durable
>> messages on durable queues are actually written to disk.
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>> For additional commands, e-mail: users-help@qpid.apache.org
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Re: How to make Qpid broker persistent?

Posted by jjw tectec <jj...@gmail.com>.
Hi Gordon,

Thanks so much for your help. I think I got this to work partially now.
The Linear Store inside the broker seems to be working, because I see the
below messages:
2015-09-03 15:39:58 [Store] info Linear Store: Most recent persistence id
found: 0x0
2015-09-03 15:39:58 [Store] info Linear Store: Recovered exchange
"topic.xxx"

However, if I create a durable exchange and send durable messages to it,
and then shutdown the broker, and restart the broker. The broker did not
retain those messages. Please see the commands and queue statistics below.
What did I do wrong?

./qpid-config -a localhost:5672 --durable add exchange topic topic.xxx
inside the publisher code, I did:
Message msg = Message(s);
msg.setDurable(1);
sender.send(msg);
Aggregate Broker Statistics: (BEFORE shutdown)
  Statistic                   Messages  Bytes
  =============================================
  queue-depth                 0         0
  total-enqueues              3         627
  total-dequeues              3         627
  persistent-enqueues         3         627
  persistent-dequeues         3         627


  Aggregate Broker Statistics: (AFTER shutdown)
  Statistic                   Messages  Bytes
  =============================================
  queue-depth                 0         0
  total-enqueues              0         0
  total-dequeues              0         0
  persistent-enqueues         0         0
  persistent-dequeues         0         0

 Thanks
 jjw

On Thu, Sep 3, 2015 at 2:29 PM, Gordon Sim <gs...@redhat.com> wrote:

> On 09/03/2015 08:16 PM, jjw tectec wrote:
>
>> Thanks for your reply. I had tried many different command options before,
>> they all had different problems. Below is the output of the execution:
>>
>> ./qpidd -p 5672 --auth no --load-module ./linearstore.so
>>
>> 2015-09-03 14:12:50 [Broker] notice Broker (pid=6278) start-up
>> 2015-09-03 14:12:50 [Store] notice Linear Store: Store module initialized;
>> store-dir=/home/mmos/.qpidd
>> 2015-09-03 14:12:50 [Store] notice Linear Store: Store module initialized;
>> store-dir=/home/mmos/.qpidd
>> 2015-09-03 14:12:50 [Broker] error Multiple store plugins are not
>> supported
>> 2015-09-03 14:12:50 [Broker] critical Broker (pid=6278) start-up failed:
>> Failed to start broker: Multiple store plugins were loaded
>> (/home/mmos/qpid/qpid-cpp-0.34/src/qpid/broker/Broker.cpp:505)
>>
>
> Ok, so this probably mean you have the store module installed into the
> default module directory. One option is to just leave out the --load-module
> ./linearstore.so. The one issue there is you need to make sure the version
> of the module you load is compatible with the qpidd binary.
>
> The other option is to add --no-module-dir i.e.
>
> ./qpidd -p 5672 --auth no --no-module-dir --load-module ./linearstore.so
> --log-enable info+
>
> That should at get the module loaded and hopefully the rest of the errors
> were related to trying to load the module twice.
>
> Once the module is loaded, the other point to note is that only durable
> messages on durable queues are actually written to disk.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>

Re: How to make Qpid broker persistent?

Posted by Gordon Sim <gs...@redhat.com>.
On 09/03/2015 08:16 PM, jjw tectec wrote:
> Thanks for your reply. I had tried many different command options before,
> they all had different problems. Below is the output of the execution:
>
> ./qpidd -p 5672 --auth no --load-module ./linearstore.so
>
> 2015-09-03 14:12:50 [Broker] notice Broker (pid=6278) start-up
> 2015-09-03 14:12:50 [Store] notice Linear Store: Store module initialized;
> store-dir=/home/mmos/.qpidd
> 2015-09-03 14:12:50 [Store] notice Linear Store: Store module initialized;
> store-dir=/home/mmos/.qpidd
> 2015-09-03 14:12:50 [Broker] error Multiple store plugins are not supported
> 2015-09-03 14:12:50 [Broker] critical Broker (pid=6278) start-up failed:
> Failed to start broker: Multiple store plugins were loaded
> (/home/mmos/qpid/qpid-cpp-0.34/src/qpid/broker/Broker.cpp:505)

Ok, so this probably mean you have the store module installed into the 
default module directory. One option is to just leave out the 
--load-module ./linearstore.so. The one issue there is you need to make 
sure the version of the module you load is compatible with the qpidd binary.

The other option is to add --no-module-dir i.e.

./qpidd -p 5672 --auth no --no-module-dir --load-module ./linearstore.so 
--log-enable info+

That should at get the module loaded and hopefully the rest of the 
errors were related to trying to load the module twice.

Once the module is loaded, the other point to note is that only durable 
messages on durable queues are actually written to disk.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Re: How to make Qpid broker persistent?

Posted by jjw tectec <jj...@gmail.com>.
Thanks for your reply. I had tried many different command options before,
they all had different problems. Below is the output of the execution:

./qpidd -p 5672 --auth no --load-module ./linearstore.so

2015-09-03 14:12:50 [Broker] notice Broker (pid=6278) start-up
2015-09-03 14:12:50 [Store] notice Linear Store: Store module initialized;
store-dir=/home/mmos/.qpidd
2015-09-03 14:12:50 [Store] notice Linear Store: Store module initialized;
store-dir=/home/mmos/.qpidd
2015-09-03 14:12:50 [Broker] error Multiple store plugins are not supported
2015-09-03 14:12:50 [Broker] critical Broker (pid=6278) start-up failed:
Failed to start broker: Multiple store plugins were loaded
(/home/mmos/qpid/qpid-cpp-0.34/src/qpid/broker/Broker.cpp:505)
linearstore: BDB0060 PANIC: fatal region error detected; run recovery
2015-09-03 14:12:50 [Store] error Linear Store: Error closing BDB
databases: Db::close: BDB0087 DB_RUNRECOVERY: Fatal error, run database
recovery
linearstore: BDB1581 File handles still open at environment close
linearstore: BDB1582 Open file handle: /home/mmos/.qpidd/qls/dat2/__db.001
linearstore: BDB1582 Open file handle: /home/mmos/.qpidd/qls/dat2/__db.002
linearstore: BDB1582 Open file handle: /home/mmos/.qpidd/qls/dat2/__db.003
linearstore: BDB1582 Open file handle: /home/mmos/.qpidd/qls/dat2/queues.db
linearstore: BDB1582 Open file handle: /home/mmos/.qpidd/qls/dat2/config.db
linearstore: BDB1582 Open file handle:
/home/mmos/.qpidd/qls/dat2/exchanges.db
linearstore: BDB1582 Open file handle:
/home/mmos/.qpidd/qls/dat2/mappings.db
linearstore: BDB1582 Open file handle:
/home/mmos/.qpidd/qls/dat2/bindings.db
linearstore: BDB1582 Open file handle: /home/mmos/.qpidd/qls/dat2/general.db
linearstore: BDB1582 Open file handle:
/home/mmos/.qpidd/qls/dat2/log.0000000001
linearstore: BDB0060 PANIC: fatal region error detected; run recovery
linearstore: BDB0060 PANIC: fatal region error detected; run recovery
linearstore: BDB0060 PANIC: fatal region error detected; run recovery
linearstore: BDB0060 PANIC: fatal region error detected; run recovery
linearstore: BDB0060 PANIC: fatal region error detected; run recovery
linearstore: BDB0060 PANIC: fatal region error detected; run recovery
2015-09-03 14:12:50 [Broker] notice Broker (pid=6278) shut-down
2015-09-03 14:12:50 [Broker] critical Unexpected error: Failed to start
broker: Multiple store plugins were loaded
(/home/mmos/qpid/qpid-cpp-0.34/src/qpid/broker/Broker.cpp:505)


=================================

./qpidd -p 5672 --config ../../etc/qpidd.conf --auth no --store-dir
~/qpid/qpid-cpp-0.34/build/src/linearstore.so

2015-09-03 14:09:26 [Broker] notice Broker (pid=6261) start-up
2015-09-03 14:09:26 [Store] error Linear Store: Journal Exception occurred
while initializing store: jexception 0x0308 jdir::exists() threw
JERR_JDIR_STAT: File stat failed.
(file="/home/mmos/qpid/qpid-cpp-0.34/build/src/linearstore.so/qls/dat2"
errno=20 (Not a directory))
2015-09-03 14:09:26 [Broker] critical Broker (pid=6261) start-up failed:
Journal Exception occurred while initializing store
(/home/mmos/qpid/qpid-cpp-0.34/src/qpid/linearstore/MessageStoreImpl.cpp:287):
jexception 0x0308 jdir::exists() threw JERR_JDIR_STAT: File stat failed.
(file="/home/mmos/qpid/qpid-cpp-0.34/build/src/linearstore.so/qls/dat2"
errno=20 (Not a directory))
2015-09-03 14:09:26 [Broker] notice Broker (pid=6261) shut-down
2015-09-03 14:09:26 [Broker] critical Unexpected error: Journal Exception
occurred while initializing store
(/home/mmos/qpid/qpid-cpp-0.34/src/qpid/linearstore/MessageStoreImpl.cpp:287):
jexception 0x0308 jdir::exists() threw JERR_JDIR_STAT: File stat failed.
(file="/home/mmos/qpid/qpid-cpp-0.34/build/src/linearstore.so/qls/dat2"
errno=20 (Not a directory))



On Thu, Sep 3, 2015 at 2:09 PM, Gordon Sim <gs...@redhat.com> wrote:

> On 09/03/2015 07:43 PM, jjw tectec wrote:
>
>> Hello,
>>
>> I'm trying to make my qpid broker persistent, but have been getting some
>> issues.
>>
>> Below is my cmake output, which indicates Legacystore disabled and
>> Linearstore enabled. (I do see linearstore.so in the build/src folder by
>> the way.)
>> -- Found BerkeleyDB: /usr/lib/x86_64-linux-gnu/libdb_cxx.so
>> -- Looking for io_queue_init in aio
>> -- Looking for io_queue_init in aio - found
>> -- Looking for include file libaio.h
>> -- Looking for include file libaio.h - found
>> -- BerkeleyDB for C++ and libaio found, Legacystore support disabled by
>> default (deprecated, use linearstore instead).
>> -- Legacystore is excluded from build.
>> -- Found BerkeleyDB: /usr/lib/x86_64-linux-gnu/libdb_cxx.so
>> -- BerkeleyDB for C++ and libaio found, Linearstore support enabled.
>> -- Including BDB from /usr/include/db_cxx.h
>> -- Building linearstore tests
>>
>> When starting the broker, using the following command (with an empty
>> qpidd.conf):
>> ./qpidd -p 5672 --config ../../etc/qpidd.conf --auth no --storage-provider
>> ./linearstore.so
>>
>
> Try:
>
>  ./qpidd -p 5672 --auth no --load-module ./linearstore.so
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>

Re: How to make Qpid broker persistent?

Posted by Gordon Sim <gs...@redhat.com>.
On 09/03/2015 07:43 PM, jjw tectec wrote:
> Hello,
>
> I'm trying to make my qpid broker persistent, but have been getting some
> issues.
>
> Below is my cmake output, which indicates Legacystore disabled and
> Linearstore enabled. (I do see linearstore.so in the build/src folder by
> the way.)
> -- Found BerkeleyDB: /usr/lib/x86_64-linux-gnu/libdb_cxx.so
> -- Looking for io_queue_init in aio
> -- Looking for io_queue_init in aio - found
> -- Looking for include file libaio.h
> -- Looking for include file libaio.h - found
> -- BerkeleyDB for C++ and libaio found, Legacystore support disabled by
> default (deprecated, use linearstore instead).
> -- Legacystore is excluded from build.
> -- Found BerkeleyDB: /usr/lib/x86_64-linux-gnu/libdb_cxx.so
> -- BerkeleyDB for C++ and libaio found, Linearstore support enabled.
> -- Including BDB from /usr/include/db_cxx.h
> -- Building linearstore tests
>
> When starting the broker, using the following command (with an empty
> qpidd.conf):
> ./qpidd -p 5672 --config ../../etc/qpidd.conf --auth no --storage-provider
> ./linearstore.so

Try:

  ./qpidd -p 5672 --auth no --load-module ./linearstore.so



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Re: How to make Qpid broker persistent?

Posted by Andrew Stitcher <as...@redhat.com>.
On Thu, 2015-09-03 at 13:43 -0500, jjw tectec wrote:
> Hello,
> 
> I'm trying to make my qpid broker persistent, but have been getting
> some
> issues.
...
> When starting the broker, using the following command (with an empty
> qpidd.conf):
> ./qpidd -p 5672 --config ../../etc/qpidd.conf --auth no --storage
> -provider
> ./linearstore.so
> 

Note that for obscure reasons the --storage-provider option is only
useful on windows (to allow the store plugin module to select between
its 2 other storage modules).

On Unix you can only have a single store loaded. I think that even
though it does nothing the store module is still built and installed!

> The console output says "no storage provider available". How can I
> specify
> a storage provider here? I thought "--storage-provider
> ./linearstore.so"
> was trying to achieve the purpose. No?

No, as above it is only useful on windows! It could be made to work on
Unix too, but so far no one has cared enough.

Andrew


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org