On Wed, 2014-03-12 at 16:14 -0700, smartdog wrote:
> I svn checkout the persistence store package. After ./bootstrap, I always get
> this error message.
We really need to do something about this!
The Persistent store has been included in the main Qpid tree for 2
releases now, you don't need to ch
I svn checkout the persistence store package. After ./bootstrap, I always get
this error message.
./configure --with-qpid-build ~/qpid-cpp-0.26/build
./configure --with-qpid-checkout ~/qpid-cpp-0.26/
./configure --with-qpid-prefix ~/qpid-cpp-0.26/
checking build system type... Invalid configurati
Thanks for the reply. I managed to get SASL start with the broker by
rebuilding. However, when I test with proton, it failed with these logs.
my endpoint
amqp://test:test1@127.0.0.1:5672/myqueue
send exe output:
recv: Connection refused
[0x99e830]:ERROR[-2] SASL header mismatch: ''
I do have a u
I've got nothing much constructive to add to this thread I'm afraid
except to plead:
can any features in this general vein be made extremely switch-off-able?
My primary requirement is for things to be as fast as possible, so
features that might interfere with that make me twitchy.
Basically I
On 12/03/14 15:53, Gordon Sim wrote:
On 03/12/2014 03:30 PM, Jan Bares wrote:
Is there easy way to send messages from one queue to another queue? I
am testing my application and I need to re-send messages from DLQ to
original queue without writing tiny application.
Assuming this is the c++ br
Anyone know why the qpid-cpp-client-devel package went MIA for CentOS6?
On Wed, Mar 12, 2014 at 6:30 PM, Gordon Sim wrote:
> The journal obviously already records the enqueues and dequeues, it just
> doesn't keep them around. One option might be to have a modified
> journal/store that kept the data for longer in some way or moved it into
> some other repository befor
On 03/12/2014 05:10 PM, Jakub Scholz wrote:
I assume the audit log doesn't need to be synced in anyway, i.e. if the
machine the broker is on has a sudden power failure, its accepted that the
activity actually recorded on disk may not be fully up to date?
Yes, I assume it would be acceptable
>
>
> I assume the audit log doesn't need to be synced in anyway, i.e. if the
> machine the broker is on has a sudden power failure, its accepted that the
> activity actually recorded on disk may not be fully up to date?
>
>
Yes, I assume it would be acceptable to lose some minor parts of
informati
On 03/11/2014 08:33 AM, Jakub Scholz wrote:
Hi Pavel,
This is definitely a feature I would be interested in :-)
Some time ago, I had a brief look at how such feature could be implemented.
My ideas were going around the *Observer interfaces (not only
QueueObserver, but also ConnectionObserver et
On 03/12/2014 03:30 PM, Jan Bares wrote:
Is there easy way to send messages from one queue to another queue? I am
testing my application and I need to re-send messages from DLQ to original
queue without writing tiny application.
Assuming this is the c++ broker, there is a QMF 'queueMoveMessag
On Mon, 2014-03-10 at 05:27 -0400, Pavel Moravec wrote:
> Hi all,
> I raised QPID-5619 to implement message auditing in C++ broker. As a new
> feature with more options of implementation and mainly configuration, I would
> like to discuss it first. Quoting the JIRA for discussion:
One possible w
Hi,
Is there easy way to send messages from one queue to another queue? I am
testing my application and I need to re-send messages from DLQ to original
queue without writing tiny application.
Thank you, Jan
Thank you, Jan
Jan Bareš
Calypso Lead Developer
In association with
WOOD & Company Fi
On Fri, 2014-03-07 at 10:35 -0800, smartdog wrote:
> Thanks for the help.
> installed this
> sudo apt-get install libsasl2-dev
>
> Unfortunately still have the same issue:
> cmake ..
> -- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
> -- Could NOT find VALGRIND (missing: VALGRIND_EXECUTA
14 matches
Mail list logo
