On 13/02/17 15:46, Chris Richardson wrote:
Gordon mentioned switching between the qpid_messaging and
qpid.messaging clients; I was slightly confused by this but hadn't got
around to inquiring further - more specific details would be really
useful. Presumably one of them is the native python clien
On 13/02/17 14:58, Alan Conway wrote:
I think we decided that making the command line tools do AMQP 1.0
wasn't solving the real problem anyway
+1
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional comma
On 13 February 2017 at 14:55, Alan Conway wrote:
> On Thu, 2017-02-09 at 15:30 +, Gordon Sim wrote:
>> On 09/02/17 15:20, Gordon Sim wrote:
>> > It seems that the swigged c++ implementation is now prefered to the
>> > pure
>> > python on. Not sure why that was done; I hadn't even realised it
>
On Mon, 2017-02-13 at 15:06 +, Gordon Sim wrote:
> On 13/02/17 15:01, Alan Conway wrote:
> > On Wed, 2017-02-08 at 11:48 +, Gordon Sim wrote:
> > > On 07/02/17 20:40, pqvchen1 wrote:
> > > > I'm trying to figure out if QPID Messaging API supports AMQP
> > > > 1.0
> > > > for ruby?
> > > > t
On Fri, 2017-02-10 at 22:46 +0100, Jakub Scholz wrote:
> Hi,
>
> I seem to be unable to build the latest master of Qpid C++ broker. It
> seems
> to complain about the round function not being in std (the complete
> output
> is below). It seems to be related to QPID-7666 / commit 34cfb7f.
>
> I'm
On Thu, 2017-02-09 at 15:30 +, Gordon Sim wrote:
> On 09/02/17 15:20, Gordon Sim wrote:
> > It seems that the swigged c++ implementation is now prefered to the
> > pure
> > python on. Not sure why that was done; I hadn't even realised it
> > had
> > been done.
>
> This was done as the fix for
On 13/02/17 15:01, Alan Conway wrote:
On Wed, 2017-02-08 at 11:48 +, Gordon Sim wrote:
On 07/02/17 20:40, pqvchen1 wrote:
I'm trying to figure out if QPID Messaging API supports AMQP 1.0
for ruby?
the document only says it supports multiple language and version
1.0, 0-10.
So Not sure if the
On Wed, 2017-02-08 at 11:48 +, Gordon Sim wrote:
> On 07/02/17 20:40, pqvchen1 wrote:
> > I'm trying to figure out if QPID Messaging API supports AMQP 1.0
> > for ruby?
> > the document only says it supports multiple language and version
> > 1.0, 0-10.
> > So Not sure if the ruby sample given i
On Fri, 2017-02-10 at 07:32 -0800, Justin Ross wrote:
> Tracked in https://issues.apache.org/jira/browse/QPID-7669
>
I think we decided that making the command line tools do AMQP 1.0
wasn't solving the real problem anyway (need a proton-based mgmt
library) so perhaps we should revertt QPID-7432.
We plan to include this in Qpid Broker for Java 6.1.2.
On 13 February 2017 at 11:04, Rob Godfrey wrote:
> As a colleague (thanks Robbie!) also pointed out to me, to workaround this
> issue in v6.1 of the broker all you need to do is get the *broker* to
> request the *client* to send "heartbeat" m
As a colleague (thanks Robbie!) also pointed out to me, to workaround this
issue in v6.1 of the broker all you need to do is get the *broker* to
request the *client* to send "heartbeat" messages more frequently than the
Jetty timeout. You can do this by adding your config.json to add a setting
for
I've raised https://issues.apache.org/jira/browse/QPID-7670 to cover this
issue, and made a change on trunk which I believe will provide the expected
behaviour wrt AMQP idle timeouts.
-- Rob
On 13 February 2017 at 00:04, Keith W wrote:
> Hi Benjamin,
>
> This is a defect in the Qpid Broker for
12 matches
Mail list logo
