It should but we have been having trouble getting to work and opened
several JIRA¹s around it. Glad we aren¹t alone in needing this capability
On 12/1/15, 5:52 PM, "Olivier Mallassi" wrote:
>I assume it works. Can someone confirm please?
>
hello all
I was wondering if qpid dispatch was supporting trnasaction. in fact the
pattern I would need to implement is the following (a classic one)
Publisher (java/c++)
beginTransaction > insert rdbms > publish msg > commit
the amqp infra would be dispatch + java qpid broker.
I assume it work
The ruby binding was broken in the 0.11 release by a mistake that was
not caught in automated testing. I've fixed the problem and improved
the automated tests, I think this might deserve a 0.11.1 as ruby is
unusable in the 0.11 release which is a severe regression.
The fix is on the 0.11.x branch:
Alex,
I have retested RC4 to ensure that the earlier defects are indeed closed.
They are, and no further issues detected.
RC4 looks good to me.
Keith
On 1 December 2015 at 17:13, Oleksandr Rudyy wrote:
> Hi everyone,
>
> After detection of couple issues with RC3 build I merged the fixes into
>
Hi everyone,
After detection of couple issues with RC3 build I merged the fixes into
6.0.x branch and produced Qpid java 6.0.0 RC4. It is available from maven
staging repo at:
https://repository.apache.org/content/repositories/orgapacheqpid-1055
RC 4 contains the following changes since RC3:
ht
Keith,
An inclusion of requested changes (r1716602 from QPID-6912 and changes
made in QPID-6923 ) is approved
On 1 December 2015 at 15:51, Keith W wrote:
> Alex,
>
> Two further issues were found whilst testing RC3. Can I request the
> following two changes for inclusion?
>
> QPID-6912 - Fix uni
Alex,
Two further issues were found whilst testing RC3. Can I request the
following two changes for inclusion?
QPID-6912 - Fix unintended change introduced by r1716602 which broke the
ability to get to the preference dialogue
This is a one line fix that rectifies a regression introduced by r171
On 12/01/2015 03:27 PM, Toralf Lund wrote:
I enabled trace via qpid::log::Logger::instance().select(...),
and got log lines containing information like
header (251 bytes); properties={{MessageProperties: content-length=23;
which is tells me most of what I need to know.
[...]
I care mainly abo
On 01/12/15 13:52, Gordon Sim wrote:
On 12/01/2015 10:38 AM, Toralf Lund wrote:
Hi,
Is there a simple way to determine the actual size of a certain message,
or alternatively, the size of headers, the QPid "framing" etc., when
using the C++ messaging API?
I'm afraid not at present.
OK.
By
Hi folks,
Qpid java 6.0.0 RC3 is now available from maven staging repo:
https://repository.apache.org/content/repositories/orgapacheqpid-1054
This build is signed and versioned for release. I am going to start voting
process for 6.0.0 release soon after sending this email.
RC 3 contains the foll
On 12/01/2015 10:38 AM, Toralf Lund wrote:
Hi,
Is there a simple way to determine the actual size of a certain message,
or alternatively, the size of headers, the QPid "framing" etc., when
using the C++ messaging API?
I'm afraid not at present.
By "actual size" I mean the size of the
informa
Keith,
All listed defect fixes are approved for inclusion into 6.0.x
Kind Regards,
Alex
On 1 December 2015 at 12:28, Keith W wrote:
> Alex,
>
> I have tested RC2:
>
> * Starting/stopping the Broker
> * Configured a new virtual host, SSL port, queue and exchange
> * Messaging using both the 0-10
Alex,
I have tested RC2:
* Starting/stopping the Broker
* Configured a new virtual host, SSL port, queue and exchange
* Messaging using both the 0-10 and 0-9 code paths using the Maven
artefacts.
* Management operations to move/copy/delete messages.
* Tested dynamically changing log level at runt
Hi,
Is there a simple way to determine the actual size of a certain message,
or alternatively, the size of headers, the QPid "framing" etc., when
using the C++ messaging API? By "actual size" I mean the size of the
information that travels across the network, as opposed to the size in
memory occu
14 matches
Mail list logo