On 02/09/2016 01:09 PM, Toralf Lund wrote:
I can reproduce the problem every time I try now. The other broker is
using the same QPid version, and I think it's supposed to be set up the
same way. It's managed by someone else (who didn't understand the error
message either when I asked), though, so
This vote is closed. It is replaced by the following:
http://qpid.2158936.n2.nabble.com/VOTE-Release-RC-2-as-Qpid-Proton-0-12-0-td7638092.html
Justin
On Mon, Feb 8, 2016 at 7:25 AM, Justin Ross wrote:
> An update. I'm going to respin today to get Andrew's fix, and then I'll
> raise a new vo
The artifacts proposed for release:
https://dist.apache.org/repos/dist/dev/qpid/proton/0.12.0-rc2/
Please indicate your vote below. If you favor releasing the 0.12.0 RC 2
bits as 0.12.0 GA, vote +1. If you have reason to think the RC is not
ready for release, vote -1.
Thanks,
Justin
RC 2 source distribution:
https://dist.apache.org/repos/dist/dev/qpid/proton/0.12.0-rc2/
Maven staging repo:
https://repository.apache.org/content/repositories/orgapacheqpid-1062
RC 2 contains two changes versus the first RC:
commit fda572f4088c5dc25be77ce6dbf847fba99a396f
Auth
On 09/02/16 12:52, Gordon Sim wrote:
On 02/09/2016 10:37 AM, Toralf Lund wrote:
On 08/02/16 18:07, Gordon Sim wrote:
When enqueing a message, the store attaches its own identifier to it
for use when dequeueing the same message. The error message indicates
that this identifier could not be obtai
On 02/09/2016 10:37 AM, Toralf Lund wrote:
On 08/02/16 18:07, Gordon Sim wrote:
When enqueing a message, the store attaches its own identifier to it
for use when dequeueing the same message. The error message indicates
that this identifier could not be obtained from the message when it
was tryin
On 08/02/16 18:07, Gordon Sim wrote:
On 02/04/2016 08:00 PM, Toralf Lund wrote:
Hi,
I've suddenly started getting exceptions with messages like
framing-error: Queue "": Dequeuing message with null
persistence Id.
(/work/build/build/qpid-0.22/cpp/src/qpid/legacystore/MessageStoreImpl.cpp:1374)"
I'm also no expert on Messenger having barely ever used it, but I
believe Gordon was suggesting you set it to a non-zero value such that
there is a window, so that you can explicitly accept/reject, rather
than the zero default where there isnt a window and you can't (with it
always accepting).
Aft
