Matt Broadstone schrieb:
> Would it be possible to fix up the .gitattributes for the qpid-cpp git
> repository? I'm having an incredibly hard time updating the sources for the
> debian packaging because there are many mixed in CRLF files throughout the
> repository (seemingly without rhyme or reaso
Hey all,
Would it be possible to fix up the .gitattributes for the qpid-cpp git
repository? I'm having an incredibly hard time updating the sources for the
debian packaging because there are many mixed in CRLF files throughout the
repository (seemingly without rhyme or reason either, i.e. not all
Gordon thanks for the quick response.
Looks like we are going to need to manage multiple sessions; one specific to
asynchronous processing and another for synchronous. Plan will be to utilize
"next_receiver" for asynchronous processing and create unique senders and
receivers for synchronous pr
On 01/09/16 17:52, Flores, Paul A. wrote:
Hi,
Working at a client site and have run into an interesting question.
The current implementation plan is to use a unique "reply to" address (queue)
to handle synchronous request reply. At this point we have a local broker so we have a
single conne
Hi,
Working at a client site and have run into an interesting question.
The current implementation plan is to use a unique "reply to" address (queue)
to handle synchronous request reply. At this point we have a local broker so we
have a single connection with a single session.
We are also p
Hi folks,
Just a heads up that I'll be looking at doing a 0.11.0 JMS client
release next week, likely cutting earlier in the week to hopefully
allow completing later in the week.
Beyond that, I'll likely skip master a little up to 0.20.0-SNAPSHOT so
it can begin taking work on implementing JMS 2
My bad - we've never exactly publicized that behavior.
:)
- Original Message -
> From: "Gordon Sim"
> To: users@qpid.apache.org
> Sent: Thursday, September 1, 2016 9:09:36 AM
> Subject: Re: Python support for AMQP 1.0?
>
> On 01/09/16 13:44, Ken Giusti wrote:
> >
> >
> > - Original
On 01/09/16 13:44, Ken Giusti wrote:
- Original Message -
From: "Gordon Sim"
To: users@qpid.apache.org
Sent: Thursday, September 1, 2016 8:32:15 AM
Subject: Re: Python support for AMQP 1.0?
On 01/09/16 09:29, Volker Diels-Grabsch wrote:
So I have to switch from a pure-Python impleme
- Original Message -
> From: "Gordon Sim"
> To: users@qpid.apache.org
> Sent: Thursday, September 1, 2016 8:32:15 AM
> Subject: Re: Python support for AMQP 1.0?
>
> On 01/09/16 09:29, Volker Diels-Grabsch wrote:
> > So I have to switch from a pure-Python implementation to a C library
>
On 01/09/16 09:29, Volker Diels-Grabsch wrote:
So I have to switch from a pure-Python implementation to a C library
with Python wrapper. This is inconvenient for deployment, but not a
show stopper for me.
I compiled qpid-proton on my own, where some questions arose:
1) Is it possible to build
Hi Volker,
I would recommend you use the python-qpid-proton package available at the pypi
repository:
https://pypi.python.org/pypi/python-qpid-proton/0.14.0
The package setup script will automagically check to see if the proton-c
library has been installed and will use it if available. Otherw
The release is approved with six binding votes in favor and none against.
On Thu, Sep 1, 2016 at 4:19 AM, Justin Ross wrote:
> +1
>
> I tested on Windows 10, Fedora 23, and Fedora 24. Windows had the same
> long-standing test failures.
>
>
>
> On Fri, Aug 26, 2016 at 4:18 PM, Justin Ross
> wro
+1
I tested on Windows 10, Fedora 23, and Fedora 24. Windows had the same
long-standing test failures.
On Fri, Aug 26, 2016 at 4:18 PM, Justin Ross wrote:
> The artifacts proposed for release:
>
> https://dist.apache.org/repos/dist/dev/qpid/cpp/1.35.0-rc/
>
> Please indicate your vote belo
Hi Volker,
You can have a look here:
https://github.com/Eurex-Clearing-Messaging-Interfaces/Python-Code-Examples
In the proton_binding subdirectory there are examples with SSL client
authentication for both blocking and non blocking connection. Hope this
helps.
Jakub
On Thu, Sep 1, 2016 at 11:
Gordon Sim schrieb:
> Use the proton library for python. There is an overview, a tutorial, some
> examples and an API reference of sorts:
> https://qpid.apache.org/proton/index.html. Feel free also to ask questions
> on this list.
Another question.
I need SSL with client cert.
That is, using the
Gordon Sim wrote
> We don't have any plan as yet (mainly because we were unaware of the
> license change really). If we can stay on the older release for now,
> that would give us time to figure out a change. What is your timeframe
> for removing BDB?
We don't have a timeframe yet (other than "
Gordon Sim schrieb:
> On 31/08/16 18:26, Volker Diels-Grabsch wrote:
> > In other words, how is a Python program meant to communicate with an
> > AMQP 1.0 server?
[...]
> Use the proton library for python. There is an overview, a tutorial, some
> examples and an API reference of sorts:
> https://qp
Hi Lorenz
Thanks for the details.
I had a feeling that if heartbeat is not set and AMQP connection is idle
for long time then it will be auto closed, hence heartbeat is set.
Also at the moment qpid broker and my application are running on same linux
machine.
Is it like I dont need heartbeat at a
Hi Ram,
I don't think the JMX plugin supports anonymous access - it always requires
a username and password (so will need to be associated with a Plain or
other password based authentication provider)
-- Rob
On 30 August 2016 at 18:56, rammohan ganapavarapu
wrote:
> Any one have any idea why m
Hello Bhargav,
there is no "best value" for heartbeating. It all depends.
Normally a TCP does not need heartbeating at all. It is usually
used for two purposes
* a simplistic sanity check that the other side is in a healthy
state (e.g., does not "hang")
* to prevent NATs or firewall from
Hi Rob
Yesterday we started qpid broker and my app in background and great news is
that it was still up and running today morning.
The issue is resolved.
Thank you very much for your prompt and accurate guidance.
I wanted to ask one more thing.
What is the best value for heartbeat, provided all
21 matches
Mail list logo
