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 Linkedin :

Re: qpid-cpp-1.35 rpm build for SUSE

Chris, SLES 12 is working fine, I had issues in SLES 11, can you try on 11? Ram On Nov 23, 2016 5:22 AM, "Chris Richardson" wrote: > Ram, > > I've tried to reproduce your problem with no success. Here are the steps I > took: > * Created a new EC2 instance of SLES 12 SP1,

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

Paolo, can you please enter a JIRA for this. Thanks. - Original Message - > From: "Paolo Patierno" > To: users@qpid.apache.org > Sent: Wednesday, November 23, 2016 10:00:28 AM > Subject: Re: Qpid Proton/Dispath trace : correlate connection identifier and > remote

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

On 11/23/2016 09:14 AM, Ganesh Murthy wrote: - Original Message - From: "Robbie Gemmell" To: users@qpid.apache.org Sent: Wednesday, November 23, 2016 7:58:48 AM Subject: Re: Qpid Proton/Dispath trace : correlate connection identifier and remote IP/port

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 on Windows Embedded &

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

Hi Ganesh, after the connection is accepted there is no other way to print the proton transport reference for the couple IP/port ? In order to have just one line of trace for it (even if we can't write it near the "Accepted ..." message). If not, I agree that the trace could be big printing

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

- Original Message - > From: "Robbie Gemmell" > To: users@qpid.apache.org > Sent: Wednesday, November 23, 2016 7:58:48 AM > Subject: Re: Qpid Proton/Dispath trace : correlate connection identifier and > remote IP/port > > On 23 November 2016 at 08:04, Paolo

Re: qpid-cpp-1.35 rpm build for SUSE

Ram, I've tried to reproduce your problem with no success. Here are the steps I took: * Created a new EC2 instance of SLES 12 SP1, ami-cae4b7dd on am3.large dual core instance type * Installed some prerequisites sudo zypper install cmake sudo zypper install gcc-c++ * Downloaded and built

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

On 23 November 2016 at 08:04, Paolo Patierno wrote: > Hi, > > > enabling the Qpid Proton trace through PN_TRACE_FRM=1 when I start the Qpid > Dispatch Router, I need sometimes to know who is the remote peer is > exchanging traced messages. > > > For example, considering

[NOTICE/DISCUSS] Making proton-j and proton-c more independent

I'd like to call this out more specifically following discussion in a couple of recent threads, to ensure folks are clear on things before they proceed. If not, shout. Following completion of the 0.16.0 release, I will look to proceed with making proton-j and proton-c (+bindings) more independent

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

+1 Regards, Adel From: Paolo Patierno Sent: Wednesday, November 23, 2016 9:04:36 AM To: users@qpid.apache.org Subject: Qpid Proton/Dispath trace : correlate connection identifier and remote IP/port Hi, enabling the Qpid Proton trace

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

Hi, enabling the Qpid Proton trace through PN_TRACE_FRM=1 when I start the Qpid Dispatch Router, I need sometimes to know who is the remote peer is exchanging traced messages. For example, considering these few lines of trace (running the Qpid Dispatch Router) : Accepted from