Re: [proton-j] handling of link-credit

... but of course with poor performance ! Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno> Blog

Re: Qpid Proton/Dispath trace : correlate connection identifier and remote IP/port

Hi Ganesh, here it is : https://issues.apache.org/jira/browse/DISPATCH-572 Thanks ! Paolo. Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : pao

Re: Qpid Proton/Dispath trace : correlate connection identifier and remote IP/port

Exactly Ted ... I got from Ganesh that it's not possible on the "Accepted ..." line but it's not necessary. So just a new log line after that when the transport reference is available to the router. Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP

Re: Qpid Proton/Dispath trace : correlate connection identifier and remote IP/port

be big printing the IP/port for every line; could be it conditional ? (i.e. using an env variable for tracing) I'm just saying that in order to have a correlation between what I see from the proton trace and Wireshark. Thanks, Paolo. Paolo Patierno Senior Software Engineer (IoT) @ Red

Qpid Proton/Dispath trace : correlate connection identifier and remote IP/port

age, i.e. : Accepted from 127.0.0.1:48192 [0x7fbc44016390] It's also true, that messages related to something like [0x7fbc44016390] come from Qpid Proton and messages like "Accepted ..." come from Qpid Dispatch Router. Thanks, Paolo. Paolo Patierno Senior Software Engine

[VOTE] Release Qpid Dispatch Router 0.7.0 (RC2)

Hi, using the 0.7.0 release I have just noticed that message annotations AREN'T LOST using message routing but they ARE LOST using link routing. Can you check this ? Thanks, Paolo. Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoT

RE: Qpid dispatch router issue

Hi, the role for the connector should be "route-container" not "on-demand". Regards, Paolo. Paolo PatiernoSenior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoTMicrosoft Azure Advisor Twitter : @ppatierno Linkedin : paolopatierno Blog : DevExperience > Date: Wed, 3 Au

RE: [Qpid dispatch router] Do we need a broker to send/receive messages?

Hi Adel, the router doesn't support the "store and forward" mechanism itself so you need to connect a broker in order to store messages. The addresses you see are all related to the management endpoint for example or reply address for the requests which comes from tools (like qdstat, qdmanage,

RE: [Qpid-Dispatch] SSL/SASL configuration on a listener

; > > > > > === > > > > > > > > > > > > > > > > > > Failure > > > > > > > > > > > > > > > > > > > From: adelbout...@live.com > &g

RE: [Qpid-Dispatch] SSL/SASL configuration on a listener

t; > > > > > > > > I also ran Wireshark and it seems that the failure is way before > > > > > establishing a connection as I have no packets being transfered in > > > > > the case of the failing certificate. > > > > > I filtered on the tcp por

RE: [Qpid-Dispatch] SSL/SASL configuration on a listener

gmur...@redhat.com > > > > To: users@qpid.apache.org > > > > Subject: Re: [Qpid-Dispatch] SSL/SASL configuration on a listener > > > > > > > > Good catch Paolo, I should note here that qdstat and qdmanage commands > > > > do *not* do hostn

RE: [Qpid-Dispatch] SSL/SASL configuration on a listener

es.apache.org/jira/browse/DISPATCH-401 which is not in master > > yet. > > > > Thanks. > > > > - Original Message - > > > From: "Paolo Patierno" > > > To: users@qpid.apache.org > > > Sent: Friday, June 24, 2016 11:09:56 AM

RE: [Qpid-Dispatch] SSL/SASL configuration on a listener

t; https://issues.apache.org/jira/browse/DISPATCH-401 which is not in master yet. > > Thanks. > > - Original Message - > > From: "Paolo Patierno" > > To: users@qpid.apache.org > > Sent: Friday, June 24, 2016 11:09:56 AM > > Subject: RE: [Qp

RE: [Qpid-Dispatch] SSL/SASL configuration on a listener

st and set the chain file > > to certDb. Here is a good explanation of certificate chain - > > https://support.dnsimple.com/articles/what-is-ssl-certificate-chain/ > > You simply create a file(call it say ca-cert-chain.pem) and populate it > > with the root CA cert and int

RE: [Qpid-Dispatch] SSL/SASL configuration on a listener

ce files to target file or use cat command) > > 2. if you are using only a root CA and *no* intermediate CA - Here you will > simply have to set the certDb to the root certificate pem file. > > Thanks. > > - Original Message - > > From: "Paolo Patierno"

RE: [Qpid-Dispatch] SSL/SASL configuration on a listener

Just a side note ... pay attention that in the SSL terminology, a self-signed certificate is a certificate issued for an entity which is signed by the entity itself. It means that in our scenario, only the root CA is a self-signed certificate. It represents the maximum level of trust you n

RE: [Qpid-Dispatch] SSL/SASL configuration on a listener

Hi Adel, I'm a bit confused of what you are trying to achieve. A listener (so acting as a server) can have only one certificate specified through certFile parameter (and related keyFile for the private key). This certificate is issued by the server (listener) to the client during SSL/T

RE: Qdstat, SASL and user with @domain

ble > in 0.7 release. > Thanks. > > ----- Original Message - > > From: "Paolo Patierno" > > To: users@qpid.apache.org > > Sent: Wednesday, June 1, 2016 11:56:08 AM > > Subject: Qdstat, SASL and user with @domain > > > > Hi all, > > >

Qdstat, SASL and user with @domain

Hi all, I have configured a router with SASL PLAIN authentication and the SASL db was created using the Cyrus tool (saslpasswd2). Using this tool you can specify or not a domain but if you don't specify it, the tool adds a default one (the machine hostname on which it's running). In any case you

RE: QPid JMS : pre-settlement at AMQP level

n the related JIRA I mentioned before. Robbie On 23 April 2016 at 19:58, Paolo Patierno wrote: > Hi Robbie, > > I already checked the source code and found this option but the parser return > an error related to unsupported option. It seems that supports only options > starting w

RE: QPid JMS : pre-settlement at AMQP level

o:robbie.gemm...@gmail.com> Sent: ‎23/‎04/‎2016 20:27 To: users@qpid.apache.org<mailto:users@qpid.apache.org> Subject: Re: QPid JMS : pre-settlement at AMQP level On 23 April 2016 at 15:56, Paolo Patierno wrote: > Hi all, > > is there a way to set the pre-settlement on the unde

QPid JMS : pre-settlement at AMQP level

Hi all, is there a way to set the pre-settlement on the underlying AMQP protocol for the JMS Qpid producers ? Thanks, Paolo Paolo PatiernoSenior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoTMicrosoft Azure Advisor Twitter : @ppatierno Linkedin : paolopatierno Blog :

Qpid Proton Engine : source filter set

Hi, am I wrong or the Qpid Proton Engine APIs haven't support for filter set on source ? I'm interested in the Java implementation. Thanks, Paolo. Paolo PatiernoSenior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoTMicrosoft Azure Advisor Twitter : @ppatierno Linkedin

RE: Rejecting/Accepting message with Qpid Proton-J

fter handling the message, which likely explains the > behaviour you saw. > > If this is something new you are working on you might be better > looking at the Reactor bits instead. From previous postings on > proton@q.a.o I believe folks from Azure Event Hubs are currently using

RE: Rejecting/Accepting message with Qpid Proton-J

ed & IoTMicrosoft Azure Advisor Twitter : @ppatierno Linkedin : paolopatierno Blog : DevExperienceBlog : Embedded101 > Date: Mon, 8 Feb 2016 18:23:39 + > From: g...@redhat.com > To: users@qpid.apache.org > Subject: Re: Rejecting/Accepting message with Qpid Proton-J > > On 02/

RE: Rejecting/Accepting message with Qpid Proton-J

e Advisor Twitter : @ppatierno Linkedin : paolopatierno Blog : DevExperienceBlog : Embedded101 > Date: Mon, 8 Feb 2016 16:55:33 + > From: g...@redhat.com > To: users@qpid.apache.org > Subject: Re: Rejecting/Accepting message with Qpid Proton-J > > On 02/06/2016 09:46 PM, Paol

Rejecting/Accepting message with Qpid Proton-J

Hello, I'm facing the following "strange" behavior with the Messenger class in the Qpid Proton-J implementation.Using ActiveMQ as AMQP broker and receiving a message, I see that calling the "reject" method on the Messenger nothing happens : the client doesn't send the disposition frame to the br

AMQP refcard typo fixed

. Regards, Paolo Patierno Sent from my Windows Phone

RE: AMQP Essentials refcard on resources page

ExperienceBlog : Embedded101 > Subject: Re: AMQP Essentials refcard on resources page > To: users@qpid.apache.org > From: tabish...@gmail.com > Date: Mon, 18 Jan 2016 09:15:29 -0500 > > On 01/18/2016 02:51 AM, Paolo Patierno wrote: > > Hi all, > > today my "AMQP Es

RE: AMQP Essentials refcard on resources page

Thanks Robbie ! Sent from my Windows Phone From: Gordon Sim Sent: ‎18/‎01/‎2016 11:21 To: users@qpid.apache.org Subject: Re: AMQP Essentials refcard on resources page On 01/18/2016 10:20 AM, Robbie Gemmell wrot

RE: AMQP Essentials refcard on resources page

t; From: g...@redhat.com > To: users@qpid.apache.org > Subject: Re: AMQP Essentials refcard on resources page > > On 01/18/2016 07:51 AM, Paolo Patierno wrote: > > Hi all, > > today my "AMQP Essentials" refcard was published on DZone web site : > > https://dzone.c

AMQP Essentials refcard on resources page

Hi all, today my "AMQP Essentials" refcard was published on DZone web site : https://dzone.com/refcardz/amqp-essentials I was wondering if it could be useful to add its link inside the resources page (https://qpid.apache.org/resources.html) of the Apache Qpid web site. Thanks,Paolo. Paolo Patiern

RE: Blog: AMQP as a Network Protocol

Very nice article Ted ! Just update my blog post on all main links about AMQP ... https://paolopatierno.wordpress.com/2015/08/30/amqp-isnt-so-scary-if-you-know-how-to-start/ Paolo PatiernoSenior Software Engineer Windows Embedded & IoTMicrosoft Azure Advisor Twitter : @ppatierno Linkedin : pao

RE: SASL mechanism different between 0.9.1 and 0.10

Hi guys, any thougths about what I wrote few days ago ? Thanks,Paolo Paolo PatiernoSenior Software Engineer Windows Embedded & IoTMicrosoft Azure Insider Twitter : @ppatierno Linkedin : paolopatierno Blog : DevExperienceBlog : Embedded101 > From: ppatie...@live.com > To: users@qpid.apache.or

RE: SASL mechanism different between 0.9.1 and 0.10

Now it seems to work but with a little bit change inside Qpid Proton C library ... As I said the in "pni_process_mechanisms" function, the SASL mechanisms list received from server is parsed and if the EXTERNAL value is found then it is selected (the function return "true") even if we set the fl

RE: SASL mechanism different between 0.9.1 and 0.10

I tried to set following ... pn_messenger_set_flags(messenger, PN_FLAGS_ALLOW_INSECURE_MECHS); without any good result. However in the pni_process_mechanisms function I see that if client receives EXTERNAL from server in the SASL mechanisms list, this is the first to be used even if I set the ab

RE: SASL mechanism different between 0.9.1 and 0.10

Yes Gordon ... You are right I'm speaking about messenger APIs Sent from my Windows Phone From: Gordon Sim Sent: ‎01/‎09/‎2015 20:39 To: users@qpid.apache.org Subject: Re: SASL mechanism different between 0.9.1

RE: SASL mechanism different between 0.9.1 and 0.10

SASL mechanism different between 0.9.1 and 0.10 On Tue, 2015-09-01 at 14:32 +, Paolo Patierno wrote: > Hi all, > I noticed the following difference between 0.9.1 and 0.10 and I'm not > able to use Qpid Proton C 0.10 for sending messages to Azure Service > Bus (a queue for

SASL mechanism different between 0.9.1 and 0.10

Hi all,I noticed the following difference between 0.9.1 and 0.10 and I'm not able to use Qpid Proton C 0.10 for sending messages to Azure Service Bus (a queue for example).The endpoint is the same for both : amqps://:@.servicebus.windows.net/q1 I'm using the "send" example in the Proton solution

RE: AW: AMQP blog

AMQP protocol in the clear but I don't think that is common practice. > Regards, > Erik > > -Ursprüngliche Nachricht- > Von: Paolo Patierno [mailto:ppatie...@live.com] > Gesendet: Freitag, 28. August 2015 08:27 > An: users@qpid.apache.org > Betreff: RE: AMQP

RE: AMQP blog

Hi Chuck, nice and very useful article ! Articles like these help people to understand better AMQP specification. I'd like to add my three part series of "AMQP type system explained by examples". I used AMQP .Net Lite too. https://paolopatierno.wordpress.com/2015/07/20/amqp-protocol-the-builtin-

Qpid Proton C : Using "engine" APIs

Hello, until today I used Qpid Proton C with "messenger" that uses engine APIs.In my understanding it seems to be possible to use engine APIs directly from the application (connection, session, link and so on) but I can't find some examples to do that.The APIs documentation doesn't show any exam

RE: Qpid Proton C : enable transport level tracing

e transport level tracing Linux: PN_TRACE_FRM=1 ./ Windows: > SET PN_TRACE_FRM=1 > - Original Message - > From: "Paolo Patierno" > To: users@qpid.apache.org > Sent: Wednesday, August 26, 2015 8:57:24 AM > Subject: Qpid Proton C : enable transport level trac

Qpid Proton C : enable transport level tracing

Hi all,until today I used Qpid Proton without tracing but now I need it at transport protocol.I want to see the AMQP messages exchanged with the broker.In the transport.c, I see that there are 4 trace levels (PN_TRACE_OFF, PN_TRACE_DRV, PN_TRACE_RAW, PN_TRACE_FRM) but I can't find a way to enabl