THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
release | store tag | trunk revision | branch |
|---|---|---|---|
0.5 | qpid-0.5-release | 3373 |
|
0.6 | qpid-0.6-release | 3793 |
|
0.8 | qpid-0.8-release | 4411 |
|
0.10 | qpid-0.10-release | 4446 |
|
0.12 | qpid-0.12-release | 4463 |
|
0.14 | qpid-0.14-release | 4490 |
|
0.16 | qpid-0.16-release | 4509 |
|
0.18 |
|
| qpid-0.18 |
To check out revision revno, use:
| Code Block |
|---|
svn co http://anonsvn.jboss.org/repos/rhmessaging/store/trunk/cpp -r [revno] [local-dir-name] |
To check out tag tagname, use:
| Code Block |
|---|
svn co http://anonsvn.jboss.org/repos/rhmessaging/store/tags/[tagname]/cpp [local-dir-name] |
To check out branch branchname, use:
| Code Block |
|---|
svn co http://anonsvn.jboss.org/repos/rhmessaging/store/branches/[branchname] [local-dir-name]
|
JavaTODO
How do I use a persistent store module?
...
For details of using the 3rd party persistent modules see here
...
...
[C+
...
+
...
store
...
]
...
What
...
is
...
a
...
RHM_IORES_ENQCAPTHRESH
...
error?
The journal ran out of space (ENQueue CAPacity THRESHold). The journal is a circular file buffer of fixed capacity set by the journal file size and number of files. When an attempt to write a record causes the journal to exceed an approx. 80% threshold, then the enqueue is rejected with this error code. Dequeues (a written record of a consumed message) may continue, however, as these free up space in the journal. Once space has been freed up, enqueues may continue as normal.
...
- The journal is too small for the size and number of messages being stored. The journal must be made large enough to hold all of the messages you expect to be on the queue at any one moment (a worst-case scenario). Make the journal capacity larger through the use of the --num-jfiles and --jfile-size-pgs parameters.
Info title Rule of thumb for sizing the journal Make the journal twice the size of all the messages you need to store at any one moment in time.
- Messages are not being dequeued (consumed) as expected. Since the store is a circular file buffer, if one un-dequeued (not consumed) message remains, it can eventually "block" the storage of new messages as the buffer gets overwritten.
...
[C+
...
+
...
store
...
]
...
What
...
is
...
the
...
TPL?
...
What
...
are
...
the
...
--tpl
...
-
...
*
...
options
...
for?
The TPL stands for Transaction Prepared List. The store creates a single instance of a journal for storing transaction boundaries called the Transaction Prepared List. Because the TPL is frequently flushed and has very different usage patterns to a normal store, it has been provided with its own set of configuration parameters:
...
If you are running from vendor RPMs, this should work automatically.
Java
| Children Display | ||
|---|---|---|
|