On 19/09/16 21:51, Flores, Paul A. wrote:
Hi,
At client site.
Performing unit tests and seeing:
terminate called after throwing an instance of 'qpid::Exception'
what(): Invalid argument (../include/qpid/sys/posix/Mutex.h:116)
Aborted
Pops up when ~Connection() is called. The
Hi,
At client site.
Performing unit tests and seeing:
terminate called after throwing an instance of 'qpid::Exception'
what(): Invalid argument (../include/qpid/sys/posix/Mutex.h:116)
Aborted
Pops up when ~Connection() is called. The destructor is getting called
automatically. We are
Hi,
I seem to have problems with building latest version of Qpid Dispatch (from
master) on some systems. In particular on Ubuntu it seems to crash with the
error below which I guess is related to the DISPATCH 511 JIRA / commit
566a1a1
Hi Adel,
It's a one-liner and it applies cleanly to the 0.6.x branch.
https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=41b7407
-Ted
On 09/19/2016 11:41 AM, Adel Boutros wrote:
Hello Ted,
Antoine is on vacation so I will be taking over this task.
Does this fix have any
On 19/09/16 16:22, Robbie Gemmell wrote:
The initial cmake step outputs a message if you are using a newer
version of proton than was marked as tested at the time of the cpp
bits being released, also detailing which version was. Given the age
of the 0.30 release, it looks like it was Proton 0.7
On 19/09/16 16:08, Vince Cole wrote:
Hi
It fails, with the following error
pn_delivery_tag_t has no member named ‘bytes’
I assume this is due to a version mismatch, between qpid 0.30 and some
other installed library (I guess its likely to be proton-c or proton-cpp,
or one of their devel
The initial cmake step outputs a message if you are using a newer
version of proton than was marked as tested at the time of the cpp
bits being released, also detailing which version was. Given the age
of the 0.30 release, it looks like it was Proton 0.7 it was released
after, though that doesn't
Hi
It fails, with the following error
pn_delivery_tag_t has no member named ‘bytes’
I assume this is due to a version mismatch, between qpid 0.30 and some
other installed library (I guess its likely to be proton-c or proton-cpp,
or one of their devel packages).
I am stuck with qpid 0.30, but