Hi,
As requested two new bug reports are filed
https://issues.apache.org/jira/browse/QPID-7089 and
https://issues.apache.org/jira/browse/QPID-7090
/Morgan
Ken Giusti wrote
> Hi Morgan,
>
> I agree - both these issues need to be addressed.
>
> Would you be willing to open two JIRA's for these
Thanks Matt -
I'll try cache cleaning. Since it's working well for you it's probably a
"pilot error" on my behalf.
-K
- Original Message -
> From: "Matt Broadstone"
> To: "Ken Giusti"
> Cc: "users" , "Irina Boverman"
> Sent: Monday, February 22, 2016 2:36:43 PM
> Subject: Re: QPID
On 22 February 2016 at 20:02, Matt Broadstone wrote:
> On Mon, Feb 22, 2016 at 2:52 PM, Matt Broadstone wrote:
>
>> Hi all,
>>
>> I'm trying to write a small test program using qpid jms to receive a
>> transfer frame with a single AMQPValue of a map32. I had expected that the
>> received message
https://pypi.python.org/pypi/python-qpid-proton/0.12.0
Let me know if there are any problems.
thanks,
--
-K
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.
On 22/02/16 19:52, Matt Broadstone wrote:
Hi all,
I'm trying to write a small test program using qpid jms to receive a
transfer frame with a single AMQPValue of a map32. I had expected that the
received message would be of type MapMessage, however I'm receiving a
JmsObjectMessage instead and I'm
On Mon, Feb 22, 2016 at 2:52 PM, Matt Broadstone wrote:
> Hi all,
>
> I'm trying to write a small test program using qpid jms to receive a
> transfer frame with a single AMQPValue of a map32. I had expected that the
> received message would be of type MapMessage, however I'm receiving a
> JmsObje
Hi all,
I'm trying to write a small test program using qpid jms to receive a
transfer frame with a single AMQPValue of a map32. I had expected that the
received message would be of type MapMessage, however I'm receiving a
JmsObjectMessage instead and I'm not quite sure how to go about pulling the
On Mon, Feb 22, 2016 at 1:24 PM, Ken Giusti wrote:
> Hi all -
>
> I've hit what looks like a packaging problem with the released QPID Proton
> packages up on our project's PPA @Launchpad.
>
> In a 'clean' Ubuntu Trusty system I added the 'released' repository and
> updated.
>
> I then attempted t
Thanks for the info Rob!
On 22/02/16 13:54, Rob Godfrey wrote:
On 22 February 2016 at 13:24, Gordon Sim wrote:
Separately on the OAuth2 thing, is there any write up/description of that?
I know similar things have been requested/discussed at one time or another
for other servers and clients. Ha
Hi all -
I've hit what looks like a packaging problem with the released QPID Proton
packages up on our project's PPA @Launchpad.
In a 'clean' Ubuntu Trusty system I added the 'released' repository and updated.
I then attempted to apt-get install libqpid-proton-dev, and got this:
$ sudo apt-get
Hello,
We are actually trying to compile qpid-proton 0.12.0 on SunOS 5.10 x86 and some
of qpid-proton's unitary tests are failing such as c-reactor-tests. After
adding some logs and debugging, we have noticed that on SunOS events are not
received by the reactor and thus nothing is added to the
Hi Morgan,
I agree - both these issues need to be addressed.
Would you be willing to open two JIRA's for these - one for the docs, the other
for the cpp broker?
http://qpid.apache.org/issues.html#report-a-bug
thanks,
-K
- Original Message -
> From: "Morgan Lindqvist"
> To: users@qp
On 20/02/16 20:48, Morgan Lindqvist wrote:
Test 6,7,8 (same massage for all three)
Here my guess is that the test is supposed to give an exception but that it
happens in the wrong place and is interpreted as a correct exception. Am I
correct in this?
--
Moving from an unrelated thread in private
On 22 February 2016 at 13:24, Gordon Sim wrote:
> On 22/02/16 13:03, Keith W wrote:
>
>>
>>
>
<... snip discussion from private@ ...>
> Separately on the OAuth2 thing, is there any write up/description of that?
> I know similar things have been re
Hi everyone,
I created a new 6.0.1 RC3 build containing a fix for a blocker:
QPID-6817 - [Java Broker] On abrupt connection close from client side when
Broker is delivering messages to consumer, the delivering messages might
not be released as part of close in some unlucky circumstances
Please t
I see RC3 is already incoming (be good to cancel the votes when you
find blocking issues) so I'll skip testing right now as previous
comments suggest things are working well.
My only comment is on the name of the src release artifact, it doesnt
match the format for 6.0.0 of the name of the root d
Hi,
The vote is canceled due to found blocker QPID-6817.
I built 6.0.1 RC3 with a fix for QPID-6817.
Please, test it and vote again in 6.0.1 RC3 voting thread.
I am sorry for inconveniences caused by cancellation.
Kind Regards,
Alex
-
The Apache Qpid community is pleased to announce the immediate availability
of Apache Qpid JMS 0.8.0.
This is the eigth release of our newer AMQP 1.0 JMS client, based around
the Qpid Proton protocol engine and implementing the AMQP JMS Mapping
as it evolves at OASIS.
The release is available now
+1
I tested the AMQP 0-10 client against Qpid C++ 0.34 & trunk and against
MRG-M 3.0 & 3.2. I also spent some time playing with the broker.
On Fri, Feb 19, 2016 at 5:01 PM, Keith W wrote:
> Hi all,
>
> A memory leak was found in RC1 (QPID-7001) so a new RC has been produced.
>
> Full list of c
19 matches
Mail list logo