You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by rammohan ganapavarapu <ra...@gmail.com> on 2016/11/01 19:20:37 UTC
Re: qpid monitoring tool in GO
I have "qpid-proton-c-0.14.0-1.el6.x86_64" installed and my borker version
is "qpid-cpp-server-1.35.0-2.el6.x86_64" so the proton-c rpm version is not
right?
Ram
On Thu, Oct 27, 2016 at 2:05 PM, Alan Conway <ac...@redhat.com> wrote:
> On Thu, 2016-10-27 at 10:16 -0700, rammohan ganapavarapu wrote:
> > Alan,
> >
> > I was trying to use this one http://godoc.org/github.com/streadway/am
> > qp
> >
> > but not sure if it will work with any qpid broker or not, i am
> > getting
> > "2016/10/27 04:09:48 Exception (501) Reason: "Exception (501) Reason:
> > \"frame could not be parsed\"""
> >
>
> First, make sure your qpidd is built & configured to support AMQP 1.0.
> The go client doesn't speak the older 0-10 version that qpidd also
> uses, but qpidd has spoken AMQP 1.0 for a long time so that shouldn't
> be a problem.
>
> Second: The Go client is a wrapper for a C library, there may be a
> mismatch between the Go code and the proton-C library you have
> installed. I would suggest downloading the latest proton release from
>
> http://qpid.apache.org/proton/
>
> and use the matching C and Go code from the release. We will figure out
> a better story for managing that relationship but we haven't yet :(
>
> Otherwise if you have to work with some specific (reasonably recent)
> older released version of proton I can help you get it working.
>
> Please let me know how you get on - like I said I'd like to add a
> generic request-response pattern to the electron package.
>
> > Thanks,
> > Ram
> >
> >
> > On Thu, Oct 27, 2016 at 7:42 AM, Alan Conway <ac...@redhat.com>
> > wrote:
> >
> > >
> > > On Wed, 2016-10-26 at 21:05 -0700, rammohan ganapavarapu wrote:
> > > >
> > > > Hi,
> > > >
> > > > I am trying to write a qpid-stat tool in go, any one attempted to
> > > > do
> > > > it, if
> > > > so can you please share your ideas? or if you have any documents
> > > > on
> > > > how to
> > > > write please share.
> > > >
> > > > Thanks,
> > > > Ram
> > >
> > > For a Go client I recommend the qpid.apache.org/electron package
> > > which
> > > is part of the Proton project.
> > >
> > > https://github.com/apache/qpid-proton/tree/master/examples/go
> > >
> > > To work with the latest you should use the code from the proton
> > > repo
> > > rather than the `go get` version as it is still progressing
> > > rapidly.
> > >
> > > qpid-stat and the other qpid tools are based on the request-
> > > response
> > > message pattern: send a correctly-formatted QMF request message
> > > with
> > > correlation-id and then process the response message. There's a
> > > "canned" request-response pattern in python at:
> > >
> > > https://github.com/apache/qpid-proton/blob/master/proton-c/bindings
> > > /pyt
> > > hon/proton/utils.py
> > >
> > > QMF messages are maps, so your main work will be to construct and
> > > interpret nested maps with the right names/values. Look at the
> > > qpid-
> > > stat sources and the qmf schemas here:
> > >
> > > /home/aconway/qpid-cpp/src/qpid/acl/management-schema.xml
> > > /home/aconway/qpid-cpp/src/qpid/broker/management-schema.xml
> > > /home/aconway/qpid-cpp/src/qpid/legacystore/management-schema.xml
> > > /home/aconway/qpid-cpp/src/qpid/ha/management-schema.xml
> > > /home/aconway/qpid-cpp/src/qpid/linearstore/management-schema.xml
> > >
> > > You are probably mostly/only interested in the broker schema.
> > >
> > > I am very interested in this as I worked on the Go binding and also
> > > on
> > > schema-driven management tools (in python) for qpid-dispatch. I
> > > would
> > > like to add a canned "request-response" pattern to the Go binding
> > > which
> > > would make your job easier, but I won't get to that in the
> > > immediate
> > > term so maybe you'll do it for me :) I'm happy to help with
> > > pointers
> > > and any problems you find in the Go binding.
> > >
> > > Cheers,
> > > Alan.
> > >
> > >
> > >
> > >
> > >
> > > -----------------------------------------------------------------
> > > ----
> > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > For additional commands, e-mail: users-help@qpid.apache.org
> > >
> > >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: qpid monitoring tool in GO
Posted by rammohan ganapavarapu <ra...@gmail.com>.
Here is the JIRA with attachments
https://issues.apache.org/jira/browse/PROTON-1356
Ram
On Fri, Nov 18, 2016 at 9:12 AM, Alan Conway <ac...@redhat.com> wrote:
> On Fri, 2016-11-18 at 07:23 -0800, rammohan ganapavarapu wrote:
> > no I was talking about email not able to deliver because the
> > attachment it
> > big, I was trying to send the tar files that you have asked, not sure
> > if
> > you received both the tar files.
>
> I only got one usr_include_proton.tgz. Open a JIRA for this issue and
> attach the files to that, that's better than putting them on the list.
>
> https://issues.apache.org/jira/
>
> That will make it easier to track as well.
>
> >
> > Ram
> >
> > On Nov 17, 2016 5:54 AM, "Alan Conway" <ac...@redhat.com> wrote:
> >
> > >
> > > On Tue, 2016-11-15 at 16:04 -0800, rammohan ganapavarapu wrote:
> > > >
> > > > Alan,
> > > >
> > > > Looks like it didn't deliver the message as its > 1mb, let me
> > > > send
> > > > you as two parts.
> > >
> > > Are you able to send smaller messages?
> > >
> > > If so that sounds like a bug, can you raise a JIRA on https://issue
> > > s.ap
> > > ache.org/jira for project: Qpid Proton, component: go-binding
> > >
> > > Add all the info you have, sample code if possible. I'll get on it
> > > ASAP.
> > >
> > > >
> > > >
> > > >
> > > > Ram
> > > >
> > > > On Tue, Nov 15, 2016 at 3:37 PM, rammohan ganapavarapu
> > > > <rammohanganap
> > > > @gmail.com> wrote:
> > > > >
> > > > > Alan,
> > > > >
> > > > > Please find the attached.
> > > > >
> > > > > Ram
> > > > >
> > > > > On Tue, Nov 15, 2016 at 8:51 AM, Alan Conway <aconway@redhat.co
> > > > > m>
> > > > > wrote:
> > > > > >
> > > > > > On Tue, 2016-11-15 at 11:48 -0500, Alan Conway wrote:
> > > > > > >
> > > > > > > On Thu, 2016-11-03 at 10:46 -0700, rammohan ganapavarapu
> > > > > > > wrote:
> > > > > > > >
> > > > > > > >
> > > > > > > > Alan,
> > > > > > > >
> > > > > > > > I have that qpid-proton-c-devel but still getting this
> > > > > > > > error
> > > > > > when
> > > > > > >
> > > > > > > >
> > > > > > > > do
> > > > > > > > go get
> > > > > > > >
> > > > > > > > # qpid.apache.org/amqp
> > > > > > > > golang/src/qpid.apache.org/amqp/types.go:33:9: expected
> > > > > > > > (unqualified)
> > > > > > > > identifier
> > > > > > > > [root@gohost ~]# rpm -qa |grep qpid-proton-c-devel
> > > > > > > > qpid-proton-c-devel-0.14.0-1.el6.x86_64
> > > > > > > >
> > > > > > > > Ram
> > > > > > > >
> > > > > > >
> > > > > > > Thanks Ram. It works for me on fedora 24 with
> > > > > > > proton-c-devel.x86_64 0.14.0-1.fc24
> > > > > > >
> > > > > > > What does `rpm -q proton-c-devel` say for you? The RHEL
> > > > > > > package
> > > > > > is
> > > > > > >
> > > > > > > probably older, I tested against past proton source
> > > > > > > releases
> > > > > > but the
> > > > > > >
> > > > > > > RHEL package may have something I missed.
> > > > > >
> > > > > > Doh! Sorry, you already did give me that info and it looks
> > > > > > like
> > > > > > the
> > > > > > same proton versin. Not sure what's happening here. Can you
> > > > > > tar
> > > > > > up your
> > > > > > golang/src/qpid.apache.org and /usr/include/proton so I can
> > > > > > look
> > > > > > at the
> > > > > > exact sources you have and see if something went astray?
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Wed, Nov 2, 2016 at 10:27 AM, Alan Conway <aconway@red
> > > > > > > > hat.
> > > > > > com>
> > > > > > >
> > > > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Tue, 2016-11-01 at 12:20 -0700, rammohan
> > > > > > > > > ganapavarapu
> > > > > > wrote:
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > I have "qpid-proton-c-0.14.0-1.el6.x86_64" installed
> > > > > > > > > > and
> > > > > > my
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > borker
> > > > > > > > > > version
> > > > > > > > > > is "qpid-cpp-server-1.35.0-2.el6.x86_64" so the
> > > > > > > > > > proton-c
> > > > > > rpm
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > version
> > > > > > > > > > is not
> > > > > > > > > > right?
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > You need qpid-proton-c-devel RPM for the header files
> > > > > > > > > which
> > > > > > are
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > used to
> > > > > > > > > compile the Go binding. With that you should be able to
> > > > > > > > >
> > > > > > > > > go get qpid.apache.org/electron
> > > > > > > > >
> > > > > > > > > Note I updated it yesterday, so if it didn't work
> > > > > > > > > before,
> > > > > > try
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > again.
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Ram
> > > > > > > > > >
> > > > > > > > > > On Thu, Oct 27, 2016 at 2:05 PM, Alan Conway <aconway
> > > > > > > > > > @red
> > > > > > hat.co
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > m>
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On Thu, 2016-10-27 at 10:16 -0700, rammohan
> > > > > > ganapavarapu
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Alan,
> > > > > > > > > > > >
> > > > > > > > > > > > I was trying to use this one http://godoc.org/git
> > > > > > > > > > > > hub.
> > > > > > com/st
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > re
> > > > > > > > > > > > adwa
> > > > > > > > > > > > y/am
> > > > > > > > > > > > qp
> > > > > > > > > > > >
> > > > > > > > > > > > but not sure if it will work with any qpid broker
> > > > > > > > > > > > or
> > > > > > not, i
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > am
> > > > > > > > > > > > getting
> > > > > > > > > > > > "2016/10/27 04:09:48 Exception (501) Reason:
> > > > > > "Exception
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > (501)
> > > > > > > > > > > > Reason:
> > > > > > > > > > > > \"frame could not be parsed\"""
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > First, make sure your qpidd is built & configured
> > > > > > > > > > > to
> > > > > > support
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > AMQP
> > > > > > > > > > > 1.0.
> > > > > > > > > > > The go client doesn't speak the older 0-10 version
> > > > > > > > > > > that
> > > > > > qpidd
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > also
> > > > > > > > > > > uses, but qpidd has spoken AMQP 1.0 for a long time
> > > > > > > > > > > so
> > > > > > that
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > shouldn't
> > > > > > > > > > > be a problem.
> > > > > > > > > > >
> > > > > > > > > > > Second: The Go client is a wrapper for a C library,
> > > > > > there may
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > be a
> > > > > > > > > > > mismatch between the Go code and the proton-C
> > > > > > > > > > > library
> > > > > > you
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > have
> > > > > > > > > > > installed. I would suggest downloading the latest
> > > > > > proton
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > release
> > > > > > > > > > > from
> > > > > > > > > > >
> > > > > > > > > > > http://qpid.apache.org/proton/
> > > > > > > > > > >
> > > > > > > > > > > and use the matching C and Go code from the
> > > > > > > > > > > release. We
> > > > > > will
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > figure
> > > > > > > > > > > out
> > > > > > > > > > > a better story for managing that relationship but
> > > > > > > > > > > we
> > > > > > haven't
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > yet :(
> > > > > > > > > > >
> > > > > > > > > > > Otherwise if you have to work with some specific
> > > > > > (reasonably
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > recent)
> > > > > > > > > > > older released version of proton I can help you get
> > > > > > > > > > > it
> > > > > > > > > > > working.
> > > > > > > > > > >
> > > > > > > > > > > Please let me know how you get on - like I said I'd
> > > > > > like to
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > add
> > > > > > > > > > > a
> > > > > > > > > > > generic request-response pattern to the electron
> > > > > > package.
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Thanks,
> > > > > > > > > > > > Ram
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > On Thu, Oct 27, 2016 at 7:42 AM, Alan Conway
> > > > > > > > > > > > <aconway
> > > > > > @redha
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > t.
> > > > > > > > > > > > com>
> > > > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Wed, 2016-10-26 at 21:05 -0700, rammohan
> > > > > > ganapavarapu
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Hi,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > I am trying to write a qpid-stat tool in go,
> > > > > > > > > > > > > > any
> > > > > > one
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > attempted to
> > > > > > > > > > > > > > do
> > > > > > > > > > > > > > it, if
> > > > > > > > > > > > > > so can you please share your ideas? or if you
> > > > > > have any
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > documents
> > > > > > > > > > > > > > on
> > > > > > > > > > > > > > how to
> > > > > > > > > > > > > > write please share.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Thanks,
> > > > > > > > > > > > > > Ram
> > > > > > > > > > > > >
> > > > > > > > > > > > > For a Go client I recommend the
> > > > > > qpid.apache.org/electron
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > package
> > > > > > > > > > > > > which
> > > > > > > > > > > > > is part of the Proton project.
> > > > > > > > > > > > >
> > > > > > > > > > > > > https://github.com/apache/qpid-proton/tree/mast
> > > > > > > > > > > > > er/e
> > > > > > xample
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > s/
> > > > > > > > > > > > > go
> > > > > > > > > > > > >
> > > > > > > > > > > > > To work with the latest you should use the code
> > > > > > from the
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > proton
> > > > > > > > > > > > > repo
> > > > > > > > > > > > > rather than the `go get` version as it is still
> > > > > > > > > > > > > progressing
> > > > > > > > > > > > > rapidly.
> > > > > > > > > > > > >
> > > > > > > > > > > > > qpid-stat and the other qpid tools are based on
> > > > > > > > > > > > > the
> > > > > > > > > > > > > request-
> > > > > > > > > > > > > response
> > > > > > > > > > > > > message pattern: send a correctly-formatted QMF
> > > > > > request
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > message
> > > > > > > > > > > > > with
> > > > > > > > > > > > > correlation-id and then process the response
> > > > > > message.
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > There's a
> > > > > > > > > > > > > "canned" request-response pattern in python at:
> > > > > > > > > > > > >
> > > > > > > > > > > > > https://github.com/apache/qpid-proton/blob/mast
> > > > > > > > > > > > > er/p
> > > > > > roton-
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > c/
> > > > > > > > > > > > > bind
> > > > > > > > > > > > > ings
> > > > > > > > > > > > > /pyt
> > > > > > > > > > > > > hon/proton/utils.py
> > > > > > > > > > > > >
> > > > > > > > > > > > > QMF messages are maps, so your main work will
> > > > > > > > > > > > > be to
> > > > > > > > > > > > > construct
> > > > > > > > > > > > > and
> > > > > > > > > > > > > interpret nested maps with the right
> > > > > > > > > > > > > names/values.
> > > > > > Look
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > at
> > > > > > > > > > > > > the
> > > > > > > > > > > > > qpid-
> > > > > > > > > > > > > stat sources and the qmf schemas here:
> > > > > > > > > > > > >
> > > > > > > > > > > > > /home/aconway/qpid-cpp/src/qpid/acl/management-
> > > > > > schema.xml
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > /home/aconway/qpid-
> > > > > > > > > > > > > cpp/src/qpid/broker/management-
> > > > > > > > > > > > > schema.xml
> > > > > > > > > > > > > /home/aconway/qpid-
> > > > > > cpp/src/qpid/legacystore/management-
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > schema.xml
> > > > > > > > > > > > > /home/aconway/qpid-cpp/src/qpid/ha/management-
> > > > > > schema.xml
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > /home/aconway/qpid-
> > > > > > cpp/src/qpid/linearstore/management-
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > schema.xml
> > > > > > > > > > > > >
> > > > > > > > > > > > > You are probably mostly/only interested in the
> > > > > > broker
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > schema.
> > > > > > > > > > > > >
> > > > > > > > > > > > > I am very interested in this as I worked on the
> > > > > > > > > > > > > Go
> > > > > > > > > > > > > binding
> > > > > > > > > > > > > and
> > > > > > > > > > > > > also
> > > > > > > > > > > > > on
> > > > > > > > > > > > > schema-driven management tools (in python) for
> > > > > > qpid-
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > dispatch. I
> > > > > > > > > > > > > would
> > > > > > > > > > > > > like to add a canned "request-response" pattern
> > > > > > > > > > > > > to
> > > > > > the Go
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > binding
> > > > > > > > > > > > > which
> > > > > > > > > > > > > would make your job easier, but I won't get to
> > > > > > > > > > > > > that
> > > > > > in
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > the
> > > > > > > > > > > > > immediate
> > > > > > > > > > > > > term so maybe you'll do it for me :) I'm happy
> > > > > > > > > > > > > to
> > > > > > help
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > with
> > > > > > > > > > > > > pointers
> > > > > > > > > > > > > and any problems you find in the Go binding.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Cheers,
> > > > > > > > > > > > > Alan.
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > ---------------------------------------------
> > > > > > > > > > > > > ----
> > > > > > --------
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > ----
> > > > > > > > > > > > > ----
> > > > > > > > > > > > > ----
> > > > > > > > > > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.
> > > > > > > > > > > > > apac
> > > > > > he.org
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > For additional commands, e-mail: users-help@qpi
> > > > > > > > > > > > > d.ap
> > > > > > ache.o
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > rg
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > -------------------------------------------------
> > > > > > > > > > > ----
> > > > > > --------
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > ----
> > > > > > > > > > > ----
> > > > > > > > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apac
> > > > > > > > > > > he.o
> > > > > > rg
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > For additional commands, e-mail: users-help@qpid.ap
> > > > > > > > > > > ache
> > > > > > .org
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > -----------------------------------------------------
> > > > > > > > > ----
> > > > > > --------
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > ----
> > > > > > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.o
> > > > > > > > > rg
> > > > > > > > > For additional commands, e-mail: users-help@qpid.apache
> > > > > > > > > .org
> > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > ---------------------------------------------------------
> > > > > > > ----
> > > > > > --------
> > > > > > >
> > > > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > > > > > For additional commands, e-mail: users-help@qpid.apache.org
> > > > > > >
> > > > > >
> > > > > >
> > > > > > -----------------------------------------------------------
> > > > > > ----
> > > > > > ------
> > > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > > > > For additional commands, e-mail: users-help@qpid.apache.org
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > > ---------------------------------------------------------------
> > > > ------
> > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > > For additional commands, e-mail: users-help@qpid.apache.org
> > >
> > >
> > > -----------------------------------------------------------------
> > > ----
> > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > For additional commands, e-mail: users-help@qpid.apache.org
> > >
> > >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: qpid monitoring tool in GO
Posted by Alan Conway <ac...@redhat.com>.
On Fri, 2016-11-18 at 07:23 -0800, rammohan ganapavarapu wrote:
> no I was talking about email not able to deliver because the
> attachment it
> big, I was trying to send the tar files that you have asked, not sure
> if
> you received both the tar files.
I only got one�usr_include_proton.tgz. Open a JIRA for this issue and
attach the files to that, that's better than putting them on the list.
https://issues.apache.org/jira/
That will make it easier to track as well.
>
> Ram
>
> On Nov 17, 2016 5:54 AM, "Alan Conway" <ac...@redhat.com> wrote:
>
> >
> > On Tue, 2016-11-15 at 16:04 -0800, rammohan ganapavarapu wrote:
> > >
> > > Alan,
> > >
> > > Looks like it didn't deliver the message as its > 1mb, let me
> > > send
> > > you as two parts.
> >
> > Are you able to send smaller messages?
> >
> > If so that sounds like a bug, can you raise a JIRA on https://issue
> > s.ap
> > ache.org/jira for project: Qpid Proton, component: go-binding
> >
> > Add all the info you have, sample code if possible. I'll get on it
> > ASAP.
> >
> > >
> > >
> > >
> > > Ram
> > >
> > > On Tue, Nov 15, 2016 at 3:37 PM, rammohan ganapavarapu
> > > <rammohanganap
> > > @gmail.com> wrote:
> > > >
> > > > Alan,
> > > >
> > > > Please find the attached.
> > > >
> > > > Ram
> > > >
> > > > On Tue, Nov 15, 2016 at 8:51 AM, Alan Conway <aconway@redhat.co
> > > > m>
> > > > wrote:
> > > > >
> > > > > On Tue, 2016-11-15 at 11:48 -0500, Alan Conway wrote:
> > > > > >
> > > > > > On Thu, 2016-11-03 at 10:46 -0700, rammohan ganapavarapu
> > > > > > wrote:
> > > > > > >
> > > > > > >
> > > > > > > Alan,
> > > > > > >
> > > > > > > I have that qpid-proton-c-devel but still getting this
> > > > > > > error
> > > > > when
> > > > > >
> > > > > > >
> > > > > > > do
> > > > > > > go get
> > > > > > >
> > > > > > > # qpid.apache.org/amqp
> > > > > > > golang/src/qpid.apache.org/amqp/types.go:33:9: expected
> > > > > > > (unqualified)
> > > > > > > identifier
> > > > > > > [root@gohost ~]# rpm -qa |grep qpid-proton-c-devel
> > > > > > > qpid-proton-c-devel-0.14.0-1.el6.x86_64
> > > > > > >
> > > > > > > Ram
> > > > > > >
> > > > > >
> > > > > > Thanks Ram. It works for me on fedora 24 with
> > > > > > ���proton-c-devel.x86_64 0.14.0-1.fc24
> > > > > >
> > > > > > What does `rpm -q proton-c-devel` say for you? The RHEL
> > > > > > package
> > > > > is
> > > > > >
> > > > > > probably older, I tested against past proton source
> > > > > > releases
> > > > > but the
> > > > > >
> > > > > > RHEL package may have something I missed.
> > > > >
> > > > > Doh! Sorry, you already did give me that info and it looks
> > > > > like
> > > > > the
> > > > > same proton versin. Not sure what's happening here. Can you
> > > > > tar
> > > > > up your
> > > > > golang/src/qpid.apache.org and /usr/include/proton so I can
> > > > > look
> > > > > at the
> > > > > exact sources you have and see if something went astray?
> > > > >
> > > > > >
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Wed, Nov 2, 2016 at 10:27 AM, Alan Conway <aconway@red
> > > > > > > hat.
> > > > > com>
> > > > > >
> > > > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Tue, 2016-11-01 at 12:20 -0700, rammohan
> > > > > > > > ganapavarapu
> > > > > wrote:
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > I have "qpid-proton-c-0.14.0-1.el6.x86_64" installed
> > > > > > > > > and
> > > > > my
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > borker
> > > > > > > > > version
> > > > > > > > > is "qpid-cpp-server-1.35.0-2.el6.x86_64" so the
> > > > > > > > > proton-c
> > > > > rpm
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > version
> > > > > > > > > is not
> > > > > > > > > right?
> > > > > > > > >
> > > > > > > >
> > > > > > > > You need qpid-proton-c-devel RPM for the header files
> > > > > > > > which
> > > > > are
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > used to
> > > > > > > > compile the Go binding. With that you should be able to
> > > > > > > >
> > > > > > > > ���go get qpid.apache.org/electron
> > > > > > > >
> > > > > > > > Note I updated it yesterday, so if it didn't work
> > > > > > > > before,
> > > > > try
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > again.
> > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Ram
> > > > > > > > >
> > > > > > > > > On Thu, Oct 27, 2016 at 2:05 PM, Alan Conway <aconway
> > > > > > > > > @red
> > > > > hat.co
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > m>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Thu, 2016-10-27 at 10:16 -0700, rammohan
> > > > > ganapavarapu
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Alan,
> > > > > > > > > > >
> > > > > > > > > > > I was trying to use this one http://godoc.org/git
> > > > > > > > > > > hub.
> > > > > com/st
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > re
> > > > > > > > > > > adwa
> > > > > > > > > > > y/am
> > > > > > > > > > > qp
> > > > > > > > > > >
> > > > > > > > > > > but not sure if it will work with any qpid broker
> > > > > > > > > > > or
> > > > > not, i
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > am
> > > > > > > > > > > getting
> > > > > > > > > > > "2016/10/27 04:09:48 Exception (501) Reason:
> > > > > "Exception
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > (501)
> > > > > > > > > > > Reason:
> > > > > > > > > > > \"frame could not be parsed\"""
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > First, make sure your qpidd is built & configured
> > > > > > > > > > to
> > > > > support
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > AMQP
> > > > > > > > > > 1.0.
> > > > > > > > > > The go client doesn't speak the older 0-10 version
> > > > > > > > > > that
> > > > > qpidd
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > also
> > > > > > > > > > uses, but qpidd has spoken AMQP 1.0 for a long time
> > > > > > > > > > so
> > > > > that
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > shouldn't
> > > > > > > > > > be a problem.
> > > > > > > > > >
> > > > > > > > > > Second: The Go client is a wrapper for a C library,
> > > > > there may
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > be a
> > > > > > > > > > mismatch between the Go code and the proton-C
> > > > > > > > > > library
> > > > > you
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > have
> > > > > > > > > > installed. I would suggest downloading the latest
> > > > > proton
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > release
> > > > > > > > > > from
> > > > > > > > > >
> > > > > > > > > > � http://qpid.apache.org/proton/
> > > > > > > > > >
> > > > > > > > > > and use the matching C and Go code from the
> > > > > > > > > > release. We
> > > > > will
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > figure
> > > > > > > > > > out
> > > > > > > > > > a better story for managing that relationship but
> > > > > > > > > > we
> > > > > haven't
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > yet :(
> > > > > > > > > >
> > > > > > > > > > Otherwise if you have to work with some specific
> > > > > (reasonably
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > recent)
> > > > > > > > > > older released version of proton I can help you get
> > > > > > > > > > it
> > > > > > > > > > working.
> > > > > > > > > >
> > > > > > > > > > Please let me know how you get on - like I said I'd
> > > > > like to
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > add
> > > > > > > > > > a
> > > > > > > > > > generic request-response pattern to the electron
> > > > > package.
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Thanks,
> > > > > > > > > > > Ram
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On Thu, Oct 27, 2016 at 7:42 AM, Alan Conway
> > > > > > > > > > > <aconway
> > > > > @redha
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > t.
> > > > > > > > > > > com>
> > > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > On Wed, 2016-10-26 at 21:05 -0700, rammohan
> > > > > ganapavarapu
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > Hi,
> > > > > > > > > > > > >
> > > > > > > > > > > > > I am trying to write a qpid-stat tool in go,
> > > > > > > > > > > > > any
> > > > > one
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > attempted to
> > > > > > > > > > > > > do
> > > > > > > > > > > > > it, if
> > > > > > > > > > > > > so can you please share your ideas? or if you
> > > > > have any
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > documents
> > > > > > > > > > > > > on
> > > > > > > > > > > > > how to
> > > > > > > > > > > > > write please share.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Thanks,
> > > > > > > > > > > > > Ram
> > > > > > > > > > > >
> > > > > > > > > > > > For a Go client I recommend the
> > > > > qpid.apache.org/electron
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > package
> > > > > > > > > > > > which
> > > > > > > > > > > > is part of the Proton project.
> > > > > > > > > > > >
> > > > > > > > > > > > https://github.com/apache/qpid-proton/tree/mast
> > > > > > > > > > > > er/e
> > > > > xample
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > s/
> > > > > > > > > > > > go
> > > > > > > > > > > >
> > > > > > > > > > > > To work with the latest you should use the code
> > > > > from the
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > proton
> > > > > > > > > > > > repo
> > > > > > > > > > > > rather than the `go get` version as it is still
> > > > > > > > > > > > progressing
> > > > > > > > > > > > rapidly.
> > > > > > > > > > > >
> > > > > > > > > > > > qpid-stat and the other qpid tools are based on
> > > > > > > > > > > > the
> > > > > > > > > > > > request-
> > > > > > > > > > > > response
> > > > > > > > > > > > message pattern: send a correctly-formatted QMF
> > > > > request
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > message
> > > > > > > > > > > > with
> > > > > > > > > > > > correlation-id and then process the response
> > > > > message.
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > There's a
> > > > > > > > > > > > "canned" request-response pattern in python at:
> > > > > > > > > > > >
> > > > > > > > > > > > https://github.com/apache/qpid-proton/blob/mast
> > > > > > > > > > > > er/p
> > > > > roton-
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > c/
> > > > > > > > > > > > bind
> > > > > > > > > > > > ings
> > > > > > > > > > > > /pyt
> > > > > > > > > > > > hon/proton/utils.py
> > > > > > > > > > > >
> > > > > > > > > > > > QMF messages are maps, so your main work will
> > > > > > > > > > > > be to
> > > > > > > > > > > > construct
> > > > > > > > > > > > and
> > > > > > > > > > > > interpret nested maps with the right
> > > > > > > > > > > > names/values.
> > > > > Look
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > at
> > > > > > > > > > > > the
> > > > > > > > > > > > qpid-
> > > > > > > > > > > > stat sources and the qmf schemas here:
> > > > > > > > > > > >
> > > > > > > > > > > > /home/aconway/qpid-cpp/src/qpid/acl/management-
> > > > > schema.xml
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > /home/aconway/qpid-
> > > > > > > > > > > > cpp/src/qpid/broker/management-
> > > > > > > > > > > > schema.xml
> > > > > > > > > > > > /home/aconway/qpid-
> > > > > cpp/src/qpid/legacystore/management-
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > schema.xml
> > > > > > > > > > > > /home/aconway/qpid-cpp/src/qpid/ha/management-
> > > > > schema.xml
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > /home/aconway/qpid-
> > > > > cpp/src/qpid/linearstore/management-
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > schema.xml
> > > > > > > > > > > >
> > > > > > > > > > > > You are probably mostly/only interested in the
> > > > > broker
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > schema.
> > > > > > > > > > > >
> > > > > > > > > > > > I am very interested in this as I worked on the
> > > > > > > > > > > > Go
> > > > > > > > > > > > binding
> > > > > > > > > > > > and
> > > > > > > > > > > > also
> > > > > > > > > > > > on
> > > > > > > > > > > > schema-driven management tools (in python) for
> > > > > qpid-
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > dispatch. I
> > > > > > > > > > > > would
> > > > > > > > > > > > like to add a canned "request-response" pattern
> > > > > > > > > > > > to
> > > > > the Go
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > binding
> > > > > > > > > > > > which
> > > > > > > > > > > > would make your job easier, but I won't get to
> > > > > > > > > > > > that
> > > > > in
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > the
> > > > > > > > > > > > immediate
> > > > > > > > > > > > term so maybe you'll do it for me :) I'm happy
> > > > > > > > > > > > to
> > > > > help
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > with
> > > > > > > > > > > > pointers
> > > > > > > > > > > > and any problems you find in the Go binding.
> > > > > > > > > > > >
> > > > > > > > > > > > Cheers,
> > > > > > > > > > > > Alan.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > ---------------------------------------------
> > > > > > > > > > > > ----
> > > > > --------
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > ----
> > > > > > > > > > > > ----
> > > > > > > > > > > > ----
> > > > > > > > > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.
> > > > > > > > > > > > apac
> > > > > he.org
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > For additional commands, e-mail: users-help@qpi
> > > > > > > > > > > > d.ap
> > > > > ache.o
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > rg
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > -------------------------------------------------
> > > > > > > > > > ----
> > > > > --------
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > ----
> > > > > > > > > > ----
> > > > > > > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apac
> > > > > > > > > > he.o
> > > > > rg
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > For additional commands, e-mail: users-help@qpid.ap
> > > > > > > > > > ache
> > > > > .org
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > -----------------------------------------------------
> > > > > > > > ----
> > > > > --------
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > ----
> > > > > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.o
> > > > > > > > rg
> > > > > > > > For additional commands, e-mail: users-help@qpid.apache
> > > > > > > > .org
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > >
> > > > > > ---------------------------------------------------------
> > > > > > ----
> > > > > --------
> > > > > >
> > > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > > > > For additional commands, e-mail: users-help@qpid.apache.org
> > > > > >
> > > > >
> > > > >
> > > > > -----------------------------------------------------------
> > > > > ----
> > > > > ------
> > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > > > For additional commands, e-mail: users-help@qpid.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------
> > > ------
> > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > For additional commands, e-mail: users-help@qpid.apache.org
> >
> >
> > -----------------------------------------------------------------
> > ----
> > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > For additional commands, e-mail: users-help@qpid.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: qpid monitoring tool in GO
Posted by rammohan ganapavarapu <ra...@gmail.com>.
no I was talking about email not able to deliver because the attachment it
big, I was trying to send the tar files that you have asked, not sure if
you received both the tar files.
Ram
On Nov 17, 2016 5:54 AM, "Alan Conway" <ac...@redhat.com> wrote:
> On Tue, 2016-11-15 at 16:04 -0800, rammohan ganapavarapu wrote:
> > Alan,
> >
> > Looks like it didn't deliver the message as its > 1mb, let me send
> > you as two parts.
>
> Are you able to send smaller messages?
>
> If so that sounds like a bug, can you raise a JIRA on https://issues.ap
> ache.org/jira for project: Qpid Proton, component: go-binding
>
> Add all the info you have, sample code if possible. I'll get on it
> ASAP.
>
> >
> >
> > Ram
> >
> > On Tue, Nov 15, 2016 at 3:37 PM, rammohan ganapavarapu <rammohanganap
> > @gmail.com> wrote:
> > > Alan,
> > >
> > > Please find the attached.
> > >
> > > Ram
> > >
> > > On Tue, Nov 15, 2016 at 8:51 AM, Alan Conway <ac...@redhat.com>
> > > wrote:
> > > > On Tue, 2016-11-15 at 11:48 -0500, Alan Conway wrote:
> > > > > On Thu, 2016-11-03 at 10:46 -0700, rammohan ganapavarapu wrote:
> > > > > >
> > > > > > Alan,
> > > > > >
> > > > > > I have that qpid-proton-c-devel but still getting this error
> > > > when
> > > > > > do
> > > > > > go get
> > > > > >
> > > > > > # qpid.apache.org/amqp
> > > > > > golang/src/qpid.apache.org/amqp/types.go:33:9: expected
> > > > > > (unqualified)
> > > > > > identifier
> > > > > > [root@gohost ~]# rpm -qa |grep qpid-proton-c-devel
> > > > > > qpid-proton-c-devel-0.14.0-1.el6.x86_64
> > > > > >
> > > > > > Ram
> > > > > >
> > > > >
> > > > > Thanks Ram. It works for me on fedora 24 with
> > > > > proton-c-devel.x86_64 0.14.0-1.fc24
> > > > >
> > > > > What does `rpm -q proton-c-devel` say for you? The RHEL package
> > > > is
> > > > > probably older, I tested against past proton source releases
> > > > but the
> > > > > RHEL package may have something I missed.
> > > >
> > > > Doh! Sorry, you already did give me that info and it looks like
> > > > the
> > > > same proton versin. Not sure what's happening here. Can you tar
> > > > up your
> > > > golang/src/qpid.apache.org and /usr/include/proton so I can look
> > > > at the
> > > > exact sources you have and see if something went astray?
> > > >
> > > > >
> > > > > >
> > > > > > On Wed, Nov 2, 2016 at 10:27 AM, Alan Conway <aconway@redhat.
> > > > com>
> > > > > > wrote:
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Tue, 2016-11-01 at 12:20 -0700, rammohan ganapavarapu
> > > > wrote:
> > > > > > > >
> > > > > > > >
> > > > > > > > I have "qpid-proton-c-0.14.0-1.el6.x86_64" installed and
> > > > my
> > > > > > > > borker
> > > > > > > > version
> > > > > > > > is "qpid-cpp-server-1.35.0-2.el6.x86_64" so the proton-c
> > > > rpm
> > > > > > > > version
> > > > > > > > is not
> > > > > > > > right?
> > > > > > > >
> > > > > > >
> > > > > > > You need qpid-proton-c-devel RPM for the header files which
> > > > are
> > > > > > > used to
> > > > > > > compile the Go binding. With that you should be able to
> > > > > > >
> > > > > > > go get qpid.apache.org/electron
> > > > > > >
> > > > > > > Note I updated it yesterday, so if it didn't work before,
> > > > try
> > > > > > > again.
> > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Ram
> > > > > > > >
> > > > > > > > On Thu, Oct 27, 2016 at 2:05 PM, Alan Conway <aconway@red
> > > > hat.co
> > > > > > > > m>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Thu, 2016-10-27 at 10:16 -0700, rammohan
> > > > ganapavarapu
> > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Alan,
> > > > > > > > > >
> > > > > > > > > > I was trying to use this one http://godoc.org/github.
> > > > com/st
> > > > > > > > > > re
> > > > > > > > > > adwa
> > > > > > > > > > y/am
> > > > > > > > > > qp
> > > > > > > > > >
> > > > > > > > > > but not sure if it will work with any qpid broker or
> > > > not, i
> > > > > > > > > > am
> > > > > > > > > > getting
> > > > > > > > > > "2016/10/27 04:09:48 Exception (501) Reason:
> > > > "Exception
> > > > > > > > > > (501)
> > > > > > > > > > Reason:
> > > > > > > > > > \"frame could not be parsed\"""
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > First, make sure your qpidd is built & configured to
> > > > support
> > > > > > > > > AMQP
> > > > > > > > > 1.0.
> > > > > > > > > The go client doesn't speak the older 0-10 version that
> > > > qpidd
> > > > > > > > > also
> > > > > > > > > uses, but qpidd has spoken AMQP 1.0 for a long time so
> > > > that
> > > > > > > > > shouldn't
> > > > > > > > > be a problem.
> > > > > > > > >
> > > > > > > > > Second: The Go client is a wrapper for a C library,
> > > > there may
> > > > > > > > > be a
> > > > > > > > > mismatch between the Go code and the proton-C library
> > > > you
> > > > > > > > > have
> > > > > > > > > installed. I would suggest downloading the latest
> > > > proton
> > > > > > > > > release
> > > > > > > > > from
> > > > > > > > >
> > > > > > > > > http://qpid.apache.org/proton/
> > > > > > > > >
> > > > > > > > > and use the matching C and Go code from the release. We
> > > > will
> > > > > > > > > figure
> > > > > > > > > out
> > > > > > > > > a better story for managing that relationship but we
> > > > haven't
> > > > > > > > > yet :(
> > > > > > > > >
> > > > > > > > > Otherwise if you have to work with some specific
> > > > (reasonably
> > > > > > > > > recent)
> > > > > > > > > older released version of proton I can help you get it
> > > > > > > > > working.
> > > > > > > > >
> > > > > > > > > Please let me know how you get on - like I said I'd
> > > > like to
> > > > > > > > > add
> > > > > > > > > a
> > > > > > > > > generic request-response pattern to the electron
> > > > package.
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Thanks,
> > > > > > > > > > Ram
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Thu, Oct 27, 2016 at 7:42 AM, Alan Conway <aconway
> > > > @redha
> > > > > > > > > > t.
> > > > > > > > > > com>
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On Wed, 2016-10-26 at 21:05 -0700, rammohan
> > > > ganapavarapu
> > > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Hi,
> > > > > > > > > > > >
> > > > > > > > > > > > I am trying to write a qpid-stat tool in go, any
> > > > one
> > > > > > > > > > > > attempted to
> > > > > > > > > > > > do
> > > > > > > > > > > > it, if
> > > > > > > > > > > > so can you please share your ideas? or if you
> > > > have any
> > > > > > > > > > > > documents
> > > > > > > > > > > > on
> > > > > > > > > > > > how to
> > > > > > > > > > > > write please share.
> > > > > > > > > > > >
> > > > > > > > > > > > Thanks,
> > > > > > > > > > > > Ram
> > > > > > > > > > >
> > > > > > > > > > > For a Go client I recommend the
> > > > qpid.apache.org/electron
> > > > > > > > > > > package
> > > > > > > > > > > which
> > > > > > > > > > > is part of the Proton project.
> > > > > > > > > > >
> > > > > > > > > > > https://github.com/apache/qpid-proton/tree/master/e
> > > > xample
> > > > > > > > > > > s/
> > > > > > > > > > > go
> > > > > > > > > > >
> > > > > > > > > > > To work with the latest you should use the code
> > > > from the
> > > > > > > > > > > proton
> > > > > > > > > > > repo
> > > > > > > > > > > rather than the `go get` version as it is still
> > > > > > > > > > > progressing
> > > > > > > > > > > rapidly.
> > > > > > > > > > >
> > > > > > > > > > > qpid-stat and the other qpid tools are based on the
> > > > > > > > > > > request-
> > > > > > > > > > > response
> > > > > > > > > > > message pattern: send a correctly-formatted QMF
> > > > request
> > > > > > > > > > > message
> > > > > > > > > > > with
> > > > > > > > > > > correlation-id and then process the response
> > > > message.
> > > > > > > > > > > There's a
> > > > > > > > > > > "canned" request-response pattern in python at:
> > > > > > > > > > >
> > > > > > > > > > > https://github.com/apache/qpid-proton/blob/master/p
> > > > roton-
> > > > > > > > > > > c/
> > > > > > > > > > > bind
> > > > > > > > > > > ings
> > > > > > > > > > > /pyt
> > > > > > > > > > > hon/proton/utils.py
> > > > > > > > > > >
> > > > > > > > > > > QMF messages are maps, so your main work will be to
> > > > > > > > > > > construct
> > > > > > > > > > > and
> > > > > > > > > > > interpret nested maps with the right names/values.
> > > > Look
> > > > > > > > > > > at
> > > > > > > > > > > the
> > > > > > > > > > > qpid-
> > > > > > > > > > > stat sources and the qmf schemas here:
> > > > > > > > > > >
> > > > > > > > > > > /home/aconway/qpid-cpp/src/qpid/acl/management-
> > > > schema.xml
> > > > > > > > > > > /home/aconway/qpid-cpp/src/qpid/broker/management-
> > > > > > > > > > > schema.xml
> > > > > > > > > > > /home/aconway/qpid-
> > > > cpp/src/qpid/legacystore/management-
> > > > > > > > > > > schema.xml
> > > > > > > > > > > /home/aconway/qpid-cpp/src/qpid/ha/management-
> > > > schema.xml
> > > > > > > > > > > /home/aconway/qpid-
> > > > cpp/src/qpid/linearstore/management-
> > > > > > > > > > > schema.xml
> > > > > > > > > > >
> > > > > > > > > > > You are probably mostly/only interested in the
> > > > broker
> > > > > > > > > > > schema.
> > > > > > > > > > >
> > > > > > > > > > > I am very interested in this as I worked on the Go
> > > > > > > > > > > binding
> > > > > > > > > > > and
> > > > > > > > > > > also
> > > > > > > > > > > on
> > > > > > > > > > > schema-driven management tools (in python) for
> > > > qpid-
> > > > > > > > > > > dispatch. I
> > > > > > > > > > > would
> > > > > > > > > > > like to add a canned "request-response" pattern to
> > > > the Go
> > > > > > > > > > > binding
> > > > > > > > > > > which
> > > > > > > > > > > would make your job easier, but I won't get to that
> > > > in
> > > > > > > > > > > the
> > > > > > > > > > > immediate
> > > > > > > > > > > term so maybe you'll do it for me :) I'm happy to
> > > > help
> > > > > > > > > > > with
> > > > > > > > > > > pointers
> > > > > > > > > > > and any problems you find in the Go binding.
> > > > > > > > > > >
> > > > > > > > > > > Cheers,
> > > > > > > > > > > Alan.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > -------------------------------------------------
> > > > --------
> > > > > > > > > > > ----
> > > > > > > > > > > ----
> > > > > > > > > > > ----
> > > > > > > > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apac
> > > > he.org
> > > > > > > > > > > For additional commands, e-mail: users-help@qpid.ap
> > > > ache.o
> > > > > > > > > > > rg
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > -----------------------------------------------------
> > > > --------
> > > > > > > > > ----
> > > > > > > > > ----
> > > > > > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.o
> > > > rg
> > > > > > > > > For additional commands, e-mail: users-help@qpid.apache
> > > > .org
> > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > ---------------------------------------------------------
> > > > --------
> > > > > > > ----
> > > > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > > > > > For additional commands, e-mail: users-help@qpid.apache.org
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > > -------------------------------------------------------------
> > > > --------
> > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > > > For additional commands, e-mail: users-help@qpid.apache.org
> > > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------
> > > > ------
> > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > > For additional commands, e-mail: users-help@qpid.apache.org
> > > >
> > > >
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > For additional commands, e-mail: users-help@qpid.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: qpid monitoring tool in GO
Posted by Alan Conway <ac...@redhat.com>.
On Tue, 2016-11-15 at 16:04 -0800, rammohan ganapavarapu wrote:
> Alan,
>
> Looks like it didn't deliver the message as its > 1mb, let me send
> you as two parts.
Are you able to send smaller messages?
If so that sounds like a bug, can you raise a JIRA on�https://issues.ap
ache.org/jira�for project: Qpid Proton, component: go-binding�
Add all the info you have, sample code if possible. I'll get on it
ASAP.
>
>
> Ram
>
> On Tue, Nov 15, 2016 at 3:37 PM, rammohan ganapavarapu <rammohanganap
> @gmail.com> wrote:
> > Alan,
> >
> > Please find the attached.
> >
> > Ram
> >
> > On Tue, Nov 15, 2016 at 8:51 AM, Alan Conway <ac...@redhat.com>
> > wrote:
> > > On Tue, 2016-11-15 at 11:48 -0500, Alan Conway wrote:
> > > > On Thu, 2016-11-03 at 10:46 -0700, rammohan ganapavarapu wrote:
> > > > >
> > > > > Alan,
> > > > >
> > > > > I have that qpid-proton-c-devel but still getting this error
> > > when
> > > > > do
> > > > > go get
> > > > >
> > > > > # qpid.apache.org/amqp
> > > > > golang/src/qpid.apache.org/amqp/types.go:33:9: expected
> > > > > (unqualified)
> > > > > identifier
> > > > > [root@gohost ~]# rpm -qa |grep qpid-proton-c-devel
> > > > > qpid-proton-c-devel-0.14.0-1.el6.x86_64
> > > > >
> > > > > Ram
> > > > >
> > > >
> > > > Thanks Ram. It works for me on fedora 24 with�
> > > > � �proton-c-devel.x86_64 0.14.0-1.fc24
> > > > �� � � � � ��
> > > > What does `rpm -q proton-c-devel` say for you? The RHEL package
> > > is
> > > > probably older, I tested against past proton source releases
> > > but the
> > > > RHEL package may have something I missed.
> > >
> > > Doh! Sorry, you already did give me that info and it looks like
> > > the
> > > same proton versin. Not sure what's happening here. Can you tar
> > > up your
> > > golang/src/qpid.apache.org and /usr/include/proton so I can look
> > > at the
> > > exact sources you have and see if something went astray?
> > >
> > > >
> > > > >
> > > > > On Wed, Nov 2, 2016 at 10:27 AM, Alan Conway <aconway@redhat.
> > > com>
> > > > > wrote:
> > > > >
> > > > > >
> > > > > >
> > > > > > On Tue, 2016-11-01 at 12:20 -0700, rammohan ganapavarapu
> > > wrote:
> > > > > > >
> > > > > > >
> > > > > > > I have "qpid-proton-c-0.14.0-1.el6.x86_64" installed and
> > > my
> > > > > > > borker
> > > > > > > version
> > > > > > > is "qpid-cpp-server-1.35.0-2.el6.x86_64" so the proton-c
> > > rpm
> > > > > > > version
> > > > > > > is not
> > > > > > > right?
> > > > > > >
> > > > > >
> > > > > > You need qpid-proton-c-devel RPM for the header files which
> > > are
> > > > > > used to
> > > > > > compile the Go binding. With that you should be able to
> > > > > >
> > > > > > ���go get qpid.apache.org/electron
> > > > > >
> > > > > > Note I updated it yesterday, so if it didn't work before,
> > > try
> > > > > > again.
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Ram
> > > > > > >
> > > > > > > On Thu, Oct 27, 2016 at 2:05 PM, Alan Conway <aconway@red
> > > hat.co
> > > > > > > m>
> > > > > > > wrote:
> > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Thu, 2016-10-27 at 10:16 -0700, rammohan
> > > ganapavarapu
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Alan,
> > > > > > > > >
> > > > > > > > > I was trying to use this one http://godoc.org/github.
> > > com/st
> > > > > > > > > re
> > > > > > > > > adwa
> > > > > > > > > y/am
> > > > > > > > > qp
> > > > > > > > >
> > > > > > > > > but not sure if it will work with any qpid broker or
> > > not, i
> > > > > > > > > am
> > > > > > > > > getting
> > > > > > > > > "2016/10/27 04:09:48 Exception (501) Reason:
> > > "Exception
> > > > > > > > > (501)
> > > > > > > > > Reason:
> > > > > > > > > \"frame could not be parsed\"""
> > > > > > > > >
> > > > > > > >
> > > > > > > > First, make sure your qpidd is built & configured to
> > > support
> > > > > > > > AMQP
> > > > > > > > 1.0.
> > > > > > > > The go client doesn't speak the older 0-10 version that
> > > qpidd
> > > > > > > > also
> > > > > > > > uses, but qpidd has spoken AMQP 1.0 for a long time so
> > > that
> > > > > > > > shouldn't
> > > > > > > > be a problem.
> > > > > > > >
> > > > > > > > Second: The Go client is a wrapper for a C library,
> > > there may
> > > > > > > > be a
> > > > > > > > mismatch between the Go code and the proton-C library
> > > you
> > > > > > > > have
> > > > > > > > installed. I would suggest downloading the latest
> > > proton
> > > > > > > > release
> > > > > > > > from
> > > > > > > >
> > > > > > > > � http://qpid.apache.org/proton/
> > > > > > > >
> > > > > > > > and use the matching C and Go code from the release. We
> > > will
> > > > > > > > figure
> > > > > > > > out
> > > > > > > > a better story for managing that relationship but we
> > > haven't
> > > > > > > > yet :(
> > > > > > > >
> > > > > > > > Otherwise if you have to work with some specific
> > > (reasonably
> > > > > > > > recent)
> > > > > > > > older released version of proton I can help you get it
> > > > > > > > working.
> > > > > > > >
> > > > > > > > Please let me know how you get on - like I said I'd
> > > like to
> > > > > > > > add
> > > > > > > > a
> > > > > > > > generic request-response pattern to the electron
> > > package.
> > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > Ram
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Thu, Oct 27, 2016 at 7:42 AM, Alan Conway <aconway
> > > @redha
> > > > > > > > > t.
> > > > > > > > > com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Wed, 2016-10-26 at 21:05 -0700, rammohan
> > > ganapavarapu
> > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Hi,
> > > > > > > > > > >
> > > > > > > > > > > I am trying to write a qpid-stat tool in go, any
> > > one
> > > > > > > > > > > attempted to
> > > > > > > > > > > do
> > > > > > > > > > > it, if
> > > > > > > > > > > so can you please share your ideas? or if you
> > > have any
> > > > > > > > > > > documents
> > > > > > > > > > > on
> > > > > > > > > > > how to
> > > > > > > > > > > write please share.
> > > > > > > > > > >
> > > > > > > > > > > Thanks,
> > > > > > > > > > > Ram
> > > > > > > > > >
> > > > > > > > > > For a Go client I recommend the
> > > qpid.apache.org/electron
> > > > > > > > > > package
> > > > > > > > > > which
> > > > > > > > > > is part of the Proton project.
> > > > > > > > > >
> > > > > > > > > > https://github.com/apache/qpid-proton/tree/master/e
> > > xample
> > > > > > > > > > s/
> > > > > > > > > > go
> > > > > > > > > >
> > > > > > > > > > To work with the latest you should use the code
> > > from the
> > > > > > > > > > proton
> > > > > > > > > > repo
> > > > > > > > > > rather than the `go get` version as it is still
> > > > > > > > > > progressing
> > > > > > > > > > rapidly.
> > > > > > > > > >
> > > > > > > > > > qpid-stat and the other qpid tools are based on the
> > > > > > > > > > request-
> > > > > > > > > > response
> > > > > > > > > > message pattern: send a correctly-formatted QMF
> > > request
> > > > > > > > > > message
> > > > > > > > > > with
> > > > > > > > > > correlation-id and then process the response
> > > message.
> > > > > > > > > > There's a
> > > > > > > > > > "canned" request-response pattern in python at:
> > > > > > > > > >
> > > > > > > > > > https://github.com/apache/qpid-proton/blob/master/p
> > > roton-
> > > > > > > > > > c/
> > > > > > > > > > bind
> > > > > > > > > > ings
> > > > > > > > > > /pyt
> > > > > > > > > > hon/proton/utils.py
> > > > > > > > > >
> > > > > > > > > > QMF messages are maps, so your main work will be to
> > > > > > > > > > construct
> > > > > > > > > > and
> > > > > > > > > > interpret nested maps with the right names/values.
> > > Look
> > > > > > > > > > at
> > > > > > > > > > the
> > > > > > > > > > qpid-
> > > > > > > > > > stat sources and the qmf schemas here:
> > > > > > > > > >
> > > > > > > > > > /home/aconway/qpid-cpp/src/qpid/acl/management-
> > > schema.xml
> > > > > > > > > > /home/aconway/qpid-cpp/src/qpid/broker/management-
> > > > > > > > > > schema.xml
> > > > > > > > > > /home/aconway/qpid-
> > > cpp/src/qpid/legacystore/management-
> > > > > > > > > > schema.xml
> > > > > > > > > > /home/aconway/qpid-cpp/src/qpid/ha/management-
> > > schema.xml
> > > > > > > > > > /home/aconway/qpid-
> > > cpp/src/qpid/linearstore/management-
> > > > > > > > > > schema.xml
> > > > > > > > > >
> > > > > > > > > > You are probably mostly/only interested in the
> > > broker
> > > > > > > > > > schema.
> > > > > > > > > >
> > > > > > > > > > I am very interested in this as I worked on the Go
> > > > > > > > > > binding
> > > > > > > > > > and
> > > > > > > > > > also
> > > > > > > > > > on
> > > > > > > > > > schema-driven management tools (in python) for
> > > qpid-
> > > > > > > > > > dispatch. I
> > > > > > > > > > would
> > > > > > > > > > like to add a canned "request-response" pattern to
> > > the Go
> > > > > > > > > > binding
> > > > > > > > > > which
> > > > > > > > > > would make your job easier, but I won't get to that
> > > in
> > > > > > > > > > the
> > > > > > > > > > immediate
> > > > > > > > > > term so maybe you'll do it for me :) I'm happy to
> > > help
> > > > > > > > > > with
> > > > > > > > > > pointers
> > > > > > > > > > and any problems you find in the Go binding.
> > > > > > > > > >
> > > > > > > > > > Cheers,
> > > > > > > > > > Alan.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > -------------------------------------------------
> > > --------
> > > > > > > > > > ----
> > > > > > > > > > ----
> > > > > > > > > > ----
> > > > > > > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apac
> > > he.org
> > > > > > > > > > For additional commands, e-mail: users-help@qpid.ap
> > > ache.o
> > > > > > > > > > rg
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > -----------------------------------------------------
> > > --------
> > > > > > > > ----
> > > > > > > > ----
> > > > > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.o
> > > rg
> > > > > > > > For additional commands, e-mail: users-help@qpid.apache
> > > .org
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > >
> > > > > > ---------------------------------------------------------
> > > --------
> > > > > > ----
> > > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > > > > For additional commands, e-mail: users-help@qpid.apache.org
> > > > > >
> > > > > >
> > > >
> > > >
> > > > -------------------------------------------------------------
> > > --------
> > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > > For additional commands, e-mail: users-help@qpid.apache.org
> > > >
> > >
> > >
> > > ---------------------------------------------------------------
> > > ------
> > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > For additional commands, e-mail: users-help@qpid.apache.org
> > >
> > >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: qpid monitoring tool in GO
Posted by rammohan ganapavarapu <ra...@gmail.com>.
Alan,
Looks like it didn't deliver the message as its > 1mb, let me send you as
two parts.
Ram
On Tue, Nov 15, 2016 at 3:37 PM, rammohan ganapavarapu <
rammohanganap@gmail.com> wrote:
> Alan,
>
> Please find the attached.
>
> Ram
>
> On Tue, Nov 15, 2016 at 8:51 AM, Alan Conway <ac...@redhat.com> wrote:
>
>> On Tue, 2016-11-15 at 11:48 -0500, Alan Conway wrote:
>> > On Thu, 2016-11-03 at 10:46 -0700, rammohan ganapavarapu wrote:
>> > >
>> > > Alan,
>> > >
>> > > I have that qpid-proton-c-devel but still getting this error when
>> > > do
>> > > go get
>> > >
>> > > # qpid.apache.org/amqp
>> > > golang/src/qpid.apache.org/amqp/types.go:33:9: expected
>> > > (unqualified)
>> > > identifier
>> > > [root@gohost ~]# rpm -qa |grep qpid-proton-c-devel
>> > > qpid-proton-c-devel-0.14.0-1.el6.x86_64
>> > >
>> > > Ram
>> > >
>> >
>> > Thanks Ram. It works for me on fedora 24 with
>> > proton-c-devel.x86_64 0.14.0-1.fc24
>> >
>> > What does `rpm -q proton-c-devel` say for you? The RHEL package is
>> > probably older, I tested against past proton source releases but the
>> > RHEL package may have something I missed.
>>
>> Doh! Sorry, you already did give me that info and it looks like the
>> same proton versin. Not sure what's happening here. Can you tar up your
>> golang/src/qpid.apache.org and /usr/include/proton so I can look at the
>> exact sources you have and see if something went astray?
>>
>> >
>> > >
>> > > On Wed, Nov 2, 2016 at 10:27 AM, Alan Conway <ac...@redhat.com>
>> > > wrote:
>> > >
>> > > >
>> > > >
>> > > > On Tue, 2016-11-01 at 12:20 -0700, rammohan ganapavarapu wrote:
>> > > > >
>> > > > >
>> > > > > I have "qpid-proton-c-0.14.0-1.el6.x86_64" installed and my
>> > > > > borker
>> > > > > version
>> > > > > is "qpid-cpp-server-1.35.0-2.el6.x86_64" so the proton-c rpm
>> > > > > version
>> > > > > is not
>> > > > > right?
>> > > > >
>> > > >
>> > > > You need qpid-proton-c-devel RPM for the header files which are
>> > > > used to
>> > > > compile the Go binding. With that you should be able to
>> > > >
>> > > > go get qpid.apache.org/electron
>> > > >
>> > > > Note I updated it yesterday, so if it didn't work before, try
>> > > > again.
>> > > >
>> > > > >
>> > > > >
>> > > > > Ram
>> > > > >
>> > > > > On Thu, Oct 27, 2016 at 2:05 PM, Alan Conway <aconway@redhat.co
>> > > > > m>
>> > > > > wrote:
>> > > > >
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > On Thu, 2016-10-27 at 10:16 -0700, rammohan ganapavarapu
>> > > > > > wrote:
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > Alan,
>> > > > > > >
>> > > > > > > I was trying to use this one http://godoc.org/github.com/st
>> > > > > > > re
>> > > > > > > adwa
>> > > > > > > y/am
>> > > > > > > qp
>> > > > > > >
>> > > > > > > but not sure if it will work with any qpid broker or not, i
>> > > > > > > am
>> > > > > > > getting
>> > > > > > > "2016/10/27 04:09:48 Exception (501) Reason: "Exception
>> > > > > > > (501)
>> > > > > > > Reason:
>> > > > > > > \"frame could not be parsed\"""
>> > > > > > >
>> > > > > >
>> > > > > > First, make sure your qpidd is built & configured to support
>> > > > > > AMQP
>> > > > > > 1.0.
>> > > > > > The go client doesn't speak the older 0-10 version that qpidd
>> > > > > > also
>> > > > > > uses, but qpidd has spoken AMQP 1.0 for a long time so that
>> > > > > > shouldn't
>> > > > > > be a problem.
>> > > > > >
>> > > > > > Second: The Go client is a wrapper for a C library, there may
>> > > > > > be a
>> > > > > > mismatch between the Go code and the proton-C library you
>> > > > > > have
>> > > > > > installed. I would suggest downloading the latest proton
>> > > > > > release
>> > > > > > from
>> > > > > >
>> > > > > > http://qpid.apache.org/proton/
>> > > > > >
>> > > > > > and use the matching C and Go code from the release. We will
>> > > > > > figure
>> > > > > > out
>> > > > > > a better story for managing that relationship but we haven't
>> > > > > > yet :(
>> > > > > >
>> > > > > > Otherwise if you have to work with some specific (reasonably
>> > > > > > recent)
>> > > > > > older released version of proton I can help you get it
>> > > > > > working.
>> > > > > >
>> > > > > > Please let me know how you get on - like I said I'd like to
>> > > > > > add
>> > > > > > a
>> > > > > > generic request-response pattern to the electron package.
>> > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > Thanks,
>> > > > > > > Ram
>> > > > > > >
>> > > > > > >
>> > > > > > > On Thu, Oct 27, 2016 at 7:42 AM, Alan Conway <aconway@redha
>> > > > > > > t.
>> > > > > > > com>
>> > > > > > > wrote:
>> > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > On Wed, 2016-10-26 at 21:05 -0700, rammohan ganapavarapu
>> > > > > > > > wrote:
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > Hi,
>> > > > > > > > >
>> > > > > > > > > I am trying to write a qpid-stat tool in go, any one
>> > > > > > > > > attempted to
>> > > > > > > > > do
>> > > > > > > > > it, if
>> > > > > > > > > so can you please share your ideas? or if you have any
>> > > > > > > > > documents
>> > > > > > > > > on
>> > > > > > > > > how to
>> > > > > > > > > write please share.
>> > > > > > > > >
>> > > > > > > > > Thanks,
>> > > > > > > > > Ram
>> > > > > > > >
>> > > > > > > > For a Go client I recommend the qpid.apache.org/electron
>> > > > > > > > package
>> > > > > > > > which
>> > > > > > > > is part of the Proton project.
>> > > > > > > >
>> > > > > > > > https://github.com/apache/qpid-proton/tree/master/example
>> > > > > > > > s/
>> > > > > > > > go
>> > > > > > > >
>> > > > > > > > To work with the latest you should use the code from the
>> > > > > > > > proton
>> > > > > > > > repo
>> > > > > > > > rather than the `go get` version as it is still
>> > > > > > > > progressing
>> > > > > > > > rapidly.
>> > > > > > > >
>> > > > > > > > qpid-stat and the other qpid tools are based on the
>> > > > > > > > request-
>> > > > > > > > response
>> > > > > > > > message pattern: send a correctly-formatted QMF request
>> > > > > > > > message
>> > > > > > > > with
>> > > > > > > > correlation-id and then process the response message.
>> > > > > > > > There's a
>> > > > > > > > "canned" request-response pattern in python at:
>> > > > > > > >
>> > > > > > > > https://github.com/apache/qpid-proton/blob/master/proton-
>> > > > > > > > c/
>> > > > > > > > bind
>> > > > > > > > ings
>> > > > > > > > /pyt
>> > > > > > > > hon/proton/utils.py
>> > > > > > > >
>> > > > > > > > QMF messages are maps, so your main work will be to
>> > > > > > > > construct
>> > > > > > > > and
>> > > > > > > > interpret nested maps with the right names/values. Look
>> > > > > > > > at
>> > > > > > > > the
>> > > > > > > > qpid-
>> > > > > > > > stat sources and the qmf schemas here:
>> > > > > > > >
>> > > > > > > > /home/aconway/qpid-cpp/src/qpid/acl/management-schema.xml
>> > > > > > > > /home/aconway/qpid-cpp/src/qpid/broker/management-
>> > > > > > > > schema.xml
>> > > > > > > > /home/aconway/qpid-cpp/src/qpid/legacystore/management-
>> > > > > > > > schema.xml
>> > > > > > > > /home/aconway/qpid-cpp/src/qpid/ha/management-schema.xml
>> > > > > > > > /home/aconway/qpid-cpp/src/qpid/linearstore/management-
>> > > > > > > > schema.xml
>> > > > > > > >
>> > > > > > > > You are probably mostly/only interested in the broker
>> > > > > > > > schema.
>> > > > > > > >
>> > > > > > > > I am very interested in this as I worked on the Go
>> > > > > > > > binding
>> > > > > > > > and
>> > > > > > > > also
>> > > > > > > > on
>> > > > > > > > schema-driven management tools (in python) for qpid-
>> > > > > > > > dispatch. I
>> > > > > > > > would
>> > > > > > > > like to add a canned "request-response" pattern to the Go
>> > > > > > > > binding
>> > > > > > > > which
>> > > > > > > > would make your job easier, but I won't get to that in
>> > > > > > > > the
>> > > > > > > > immediate
>> > > > > > > > term so maybe you'll do it for me :) I'm happy to help
>> > > > > > > > with
>> > > > > > > > pointers
>> > > > > > > > and any problems you find in the Go binding.
>> > > > > > > >
>> > > > > > > > Cheers,
>> > > > > > > > Alan.
>> > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > ---------------------------------------------------------
>> > > > > > > > ----
>> > > > > > > > ----
>> > > > > > > > ----
>> > > > > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>> > > > > > > > For additional commands, e-mail: users-help@qpid.apache.o
>> > > > > > > > rg
>> > > > > > > >
>> > > > > > > >
>> > > > > >
>> > > > > >
>> > > > > > -------------------------------------------------------------
>> > > > > > ----
>> > > > > > ----
>> > > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>> > > > > > For additional commands, e-mail: users-help@qpid.apache.org
>> > > > > >
>> > > > > >
>> > > >
>> > > >
>> > > > -----------------------------------------------------------------
>> > > > ----
>> > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>> > > > For additional commands, e-mail: users-help@qpid.apache.org
>> > > >
>> > > >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>> > For additional commands, e-mail: users-help@qpid.apache.org
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>> For additional commands, e-mail: users-help@qpid.apache.org
>>
>>
>
Re: qpid monitoring tool in GO
Posted by Alan Conway <ac...@redhat.com>.
On Tue, 2016-11-15 at 11:48 -0500, Alan Conway wrote:
> On Thu, 2016-11-03 at 10:46 -0700, rammohan ganapavarapu wrote:
> >
> > Alan,
> >
> > I have that qpid-proton-c-devel but still getting this error when
> > do
> > go get
> >
> > # qpid.apache.org/amqp
> > golang/src/qpid.apache.org/amqp/types.go:33:9: expected
> > (unqualified)
> > identifier
> > [root@gohost ~]# rpm -qa |grep qpid-proton-c-devel
> > qpid-proton-c-devel-0.14.0-1.el6.x86_64
> >
> > Ram
> >
>
> Thanks Ram. It works for me on fedora 24 with�
> � �proton-c-devel.x86_64 0.14.0-1.fc24
> �� � � � � ��
> What does `rpm -q proton-c-devel` say for you? The RHEL package is
> probably older, I tested against past proton source releases but the
> RHEL package may have something I missed.
Doh! Sorry, you already did give me that info and it looks like the
same proton versin. Not sure what's happening here. Can you tar up your
golang/src/qpid.apache.org and /usr/include/proton so I can look at the
exact sources you have and see if something went astray?
>
> >
> > On Wed, Nov 2, 2016 at 10:27 AM, Alan Conway <ac...@redhat.com>
> > wrote:
> >
> > >
> > >
> > > On Tue, 2016-11-01 at 12:20 -0700, rammohan ganapavarapu wrote:
> > > >
> > > >
> > > > I have "qpid-proton-c-0.14.0-1.el6.x86_64" installed and my
> > > > borker
> > > > version
> > > > is "qpid-cpp-server-1.35.0-2.el6.x86_64" so the proton-c rpm
> > > > version
> > > > is not
> > > > right?
> > > >
> > >
> > > You need qpid-proton-c-devel RPM for the header files which are
> > > used to
> > > compile the Go binding. With that you should be able to
> > >
> > > ���go get qpid.apache.org/electron
> > >
> > > Note I updated it yesterday, so if it didn't work before, try
> > > again.
> > >
> > > >
> > > >
> > > > Ram
> > > >
> > > > On Thu, Oct 27, 2016 at 2:05 PM, Alan Conway <aconway@redhat.co
> > > > m>
> > > > wrote:
> > > >
> > > > >
> > > > >
> > > > >
> > > > > On Thu, 2016-10-27 at 10:16 -0700, rammohan ganapavarapu
> > > > > wrote:
> > > > > >
> > > > > >
> > > > > >
> > > > > > Alan,
> > > > > >
> > > > > > I was trying to use this one http://godoc.org/github.com/st
> > > > > > re
> > > > > > adwa
> > > > > > y/am
> > > > > > qp
> > > > > >
> > > > > > but not sure if it will work with any qpid broker or not, i
> > > > > > am
> > > > > > getting
> > > > > > "2016/10/27 04:09:48 Exception (501) Reason: "Exception
> > > > > > (501)
> > > > > > Reason:
> > > > > > \"frame could not be parsed\"""
> > > > > >
> > > > >
> > > > > First, make sure your qpidd is built & configured to support
> > > > > AMQP
> > > > > 1.0.
> > > > > The go client doesn't speak the older 0-10 version that qpidd
> > > > > also
> > > > > uses, but qpidd has spoken AMQP 1.0 for a long time so that
> > > > > shouldn't
> > > > > be a problem.
> > > > >
> > > > > Second: The Go client is a wrapper for a C library, there may
> > > > > be a
> > > > > mismatch between the Go code and the proton-C library you
> > > > > have
> > > > > installed. I would suggest downloading the latest proton
> > > > > release
> > > > > from
> > > > >
> > > > > � http://qpid.apache.org/proton/
> > > > >
> > > > > and use the matching C and Go code from the release. We will
> > > > > figure
> > > > > out
> > > > > a better story for managing that relationship but we haven't
> > > > > yet :(
> > > > >
> > > > > Otherwise if you have to work with some specific (reasonably
> > > > > recent)
> > > > > older released version of proton I can help you get it
> > > > > working.
> > > > >
> > > > > Please let me know how you get on - like I said I'd like to
> > > > > add
> > > > > a
> > > > > generic request-response pattern to the electron package.
> > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Thanks,
> > > > > > Ram
> > > > > >
> > > > > >
> > > > > > On Thu, Oct 27, 2016 at 7:42 AM, Alan Conway <aconway@redha
> > > > > > t.
> > > > > > com>
> > > > > > wrote:
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Wed, 2016-10-26 at 21:05 -0700, rammohan ganapavarapu
> > > > > > > wrote:
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > I am trying to write a qpid-stat tool in go, any one
> > > > > > > > attempted to
> > > > > > > > do
> > > > > > > > it, if
> > > > > > > > so can you please share your ideas? or if you have any
> > > > > > > > documents
> > > > > > > > on
> > > > > > > > how to
> > > > > > > > write please share.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Ram
> > > > > > >
> > > > > > > For a Go client I recommend the qpid.apache.org/electron
> > > > > > > package
> > > > > > > which
> > > > > > > is part of the Proton project.
> > > > > > >
> > > > > > > https://github.com/apache/qpid-proton/tree/master/example
> > > > > > > s/
> > > > > > > go
> > > > > > >
> > > > > > > To work with the latest you should use the code from the
> > > > > > > proton
> > > > > > > repo
> > > > > > > rather than the `go get` version as it is still
> > > > > > > progressing
> > > > > > > rapidly.
> > > > > > >
> > > > > > > qpid-stat and the other qpid tools are based on the
> > > > > > > request-
> > > > > > > response
> > > > > > > message pattern: send a correctly-formatted QMF request
> > > > > > > message
> > > > > > > with
> > > > > > > correlation-id and then process the response message.
> > > > > > > There's a
> > > > > > > "canned" request-response pattern in python at:
> > > > > > >
> > > > > > > https://github.com/apache/qpid-proton/blob/master/proton-
> > > > > > > c/
> > > > > > > bind
> > > > > > > ings
> > > > > > > /pyt
> > > > > > > hon/proton/utils.py
> > > > > > >
> > > > > > > QMF messages are maps, so your main work will be to
> > > > > > > construct
> > > > > > > and
> > > > > > > interpret nested maps with the right names/values. Look
> > > > > > > at
> > > > > > > the
> > > > > > > qpid-
> > > > > > > stat sources and the qmf schemas here:
> > > > > > >
> > > > > > > /home/aconway/qpid-cpp/src/qpid/acl/management-schema.xml
> > > > > > > /home/aconway/qpid-cpp/src/qpid/broker/management-
> > > > > > > schema.xml
> > > > > > > /home/aconway/qpid-cpp/src/qpid/legacystore/management-
> > > > > > > schema.xml
> > > > > > > /home/aconway/qpid-cpp/src/qpid/ha/management-schema.xml
> > > > > > > /home/aconway/qpid-cpp/src/qpid/linearstore/management-
> > > > > > > schema.xml
> > > > > > >
> > > > > > > You are probably mostly/only interested in the broker
> > > > > > > schema.
> > > > > > >
> > > > > > > I am very interested in this as I worked on the Go
> > > > > > > binding
> > > > > > > and
> > > > > > > also
> > > > > > > on
> > > > > > > schema-driven management tools (in python) for qpid-
> > > > > > > dispatch. I
> > > > > > > would
> > > > > > > like to add a canned "request-response" pattern to the Go
> > > > > > > binding
> > > > > > > which
> > > > > > > would make your job easier, but I won't get to that in
> > > > > > > the
> > > > > > > immediate
> > > > > > > term so maybe you'll do it for me :) I'm happy to help
> > > > > > > with
> > > > > > > pointers
> > > > > > > and any problems you find in the Go binding.
> > > > > > >
> > > > > > > Cheers,
> > > > > > > Alan.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > ---------------------------------------------------------
> > > > > > > ----
> > > > > > > ----
> > > > > > > ----
> > > > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > > > > > For additional commands, e-mail: users-help@qpid.apache.o
> > > > > > > rg
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > > -------------------------------------------------------------
> > > > > ----
> > > > > ----
> > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > > > For additional commands, e-mail: users-help@qpid.apache.org
> > > > >
> > > > >
> > >
> > >
> > > -----------------------------------------------------------------
> > > ----
> > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > For additional commands, e-mail: users-help@qpid.apache.org
> > >
> > >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: qpid monitoring tool in GO
Posted by Alan Conway <ac...@redhat.com>.
On Thu, 2016-11-03 at 10:46 -0700, rammohan ganapavarapu wrote:
> Alan,
>
> I have that qpid-proton-c-devel but still getting this error when do
> go get
>
> # qpid.apache.org/amqp
> golang/src/qpid.apache.org/amqp/types.go:33:9: expected (unqualified)
> identifier
> [root@gohost ~]# rpm -qa |grep qpid-proton-c-devel
> qpid-proton-c-devel-0.14.0-1.el6.x86_64
>
> Ram
>
Thanks Ram. It works for me on fedora 24 with�
� �proton-c-devel.x86_64 0.14.0-1.fc24
�� � � � � ��
What does `rpm -q proton-c-devel` say for you? The RHEL package is
probably older, I tested against past proton source releases but the
RHEL package may have something I missed.
> On Wed, Nov 2, 2016 at 10:27 AM, Alan Conway <ac...@redhat.com>
> wrote:
>
> >
> > On Tue, 2016-11-01 at 12:20 -0700, rammohan ganapavarapu wrote:
> > >
> > > I have "qpid-proton-c-0.14.0-1.el6.x86_64" installed and my
> > > borker
> > > version
> > > is "qpid-cpp-server-1.35.0-2.el6.x86_64" so the proton-c rpm
> > > version
> > > is not
> > > right?
> > >
> >
> > You need qpid-proton-c-devel RPM for the header files which are
> > used to
> > compile the Go binding. With that you should be able to
> >
> > ���go get qpid.apache.org/electron
> >
> > Note I updated it yesterday, so if it didn't work before, try
> > again.
> >
> > >
> > > Ram
> > >
> > > On Thu, Oct 27, 2016 at 2:05 PM, Alan Conway <ac...@redhat.com>
> > > wrote:
> > >
> > > >
> > > >
> > > > On Thu, 2016-10-27 at 10:16 -0700, rammohan ganapavarapu wrote:
> > > > >
> > > > >
> > > > > Alan,
> > > > >
> > > > > I was trying to use this one http://godoc.org/github.com/stre
> > > > > adwa
> > > > > y/am
> > > > > qp
> > > > >
> > > > > but not sure if it will work with any qpid broker or not, i
> > > > > am
> > > > > getting
> > > > > "2016/10/27 04:09:48 Exception (501) Reason: "Exception (501)
> > > > > Reason:
> > > > > \"frame could not be parsed\"""
> > > > >
> > > >
> > > > First, make sure your qpidd is built & configured to support
> > > > AMQP
> > > > 1.0.
> > > > The go client doesn't speak the older 0-10 version that qpidd
> > > > also
> > > > uses, but qpidd has spoken AMQP 1.0 for a long time so that
> > > > shouldn't
> > > > be a problem.
> > > >
> > > > Second: The Go client is a wrapper for a C library, there may
> > > > be a
> > > > mismatch between the Go code and the proton-C library you have
> > > > installed. I would suggest downloading the latest proton
> > > > release
> > > > from
> > > >
> > > > � http://qpid.apache.org/proton/
> > > >
> > > > and use the matching C and Go code from the release. We will
> > > > figure
> > > > out
> > > > a better story for managing that relationship but we haven't
> > > > yet :(
> > > >
> > > > Otherwise if you have to work with some specific (reasonably
> > > > recent)
> > > > older released version of proton I can help you get it working.
> > > >
> > > > Please let me know how you get on - like I said I'd like to add
> > > > a
> > > > generic request-response pattern to the electron package.
> > > >
> > > > >
> > > > >
> > > > > Thanks,
> > > > > Ram
> > > > >
> > > > >
> > > > > On Thu, Oct 27, 2016 at 7:42 AM, Alan Conway <aconway@redhat.
> > > > > com>
> > > > > wrote:
> > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Wed, 2016-10-26 at 21:05 -0700, rammohan ganapavarapu
> > > > > > wrote:
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > I am trying to write a qpid-stat tool in go, any one
> > > > > > > attempted to
> > > > > > > do
> > > > > > > it, if
> > > > > > > so can you please share your ideas? or if you have any
> > > > > > > documents
> > > > > > > on
> > > > > > > how to
> > > > > > > write please share.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Ram
> > > > > >
> > > > > > For a Go client I recommend the qpid.apache.org/electron
> > > > > > package
> > > > > > which
> > > > > > is part of the Proton project.
> > > > > >
> > > > > > https://github.com/apache/qpid-proton/tree/master/examples/
> > > > > > go
> > > > > >
> > > > > > To work with the latest you should use the code from the
> > > > > > proton
> > > > > > repo
> > > > > > rather than the `go get` version as it is still progressing
> > > > > > rapidly.
> > > > > >
> > > > > > qpid-stat and the other qpid tools are based on the
> > > > > > request-
> > > > > > response
> > > > > > message pattern: send a correctly-formatted QMF request
> > > > > > message
> > > > > > with
> > > > > > correlation-id and then process the response message.
> > > > > > There's a
> > > > > > "canned" request-response pattern in python at:
> > > > > >
> > > > > > https://github.com/apache/qpid-proton/blob/master/proton-c/
> > > > > > bind
> > > > > > ings
> > > > > > /pyt
> > > > > > hon/proton/utils.py
> > > > > >
> > > > > > QMF messages are maps, so your main work will be to
> > > > > > construct
> > > > > > and
> > > > > > interpret nested maps with the right names/values. Look at
> > > > > > the
> > > > > > qpid-
> > > > > > stat sources and the qmf schemas here:
> > > > > >
> > > > > > /home/aconway/qpid-cpp/src/qpid/acl/management-schema.xml
> > > > > > /home/aconway/qpid-cpp/src/qpid/broker/management-
> > > > > > schema.xml
> > > > > > /home/aconway/qpid-cpp/src/qpid/legacystore/management-
> > > > > > schema.xml
> > > > > > /home/aconway/qpid-cpp/src/qpid/ha/management-schema.xml
> > > > > > /home/aconway/qpid-cpp/src/qpid/linearstore/management-
> > > > > > schema.xml
> > > > > >
> > > > > > You are probably mostly/only interested in the broker
> > > > > > schema.
> > > > > >
> > > > > > I am very interested in this as I worked on the Go binding
> > > > > > and
> > > > > > also
> > > > > > on
> > > > > > schema-driven management tools (in python) for qpid-
> > > > > > dispatch. I
> > > > > > would
> > > > > > like to add a canned "request-response" pattern to the Go
> > > > > > binding
> > > > > > which
> > > > > > would make your job easier, but I won't get to that in the
> > > > > > immediate
> > > > > > term so maybe you'll do it for me :) I'm happy to help with
> > > > > > pointers
> > > > > > and any problems you find in the Go binding.
> > > > > >
> > > > > > Cheers,
> > > > > > Alan.
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > ---------------------------------------------------------
> > > > > > ----
> > > > > > ----
> > > > > > ----
> > > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > > > > For additional commands, e-mail: users-help@qpid.apache.org
> > > > > >
> > > > > >
> > > >
> > > >
> > > > -------------------------------------------------------------
> > > > ----
> > > > ----
> > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > > For additional commands, e-mail: users-help@qpid.apache.org
> > > >
> > > >
> >
> >
> > -----------------------------------------------------------------
> > ----
> > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > For additional commands, e-mail: users-help@qpid.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: qpid monitoring tool in GO
Posted by rammohan ganapavarapu <ra...@gmail.com>.
Alan,
I have that qpid-proton-c-devel but still getting this error when do go get
# qpid.apache.org/amqp
golang/src/qpid.apache.org/amqp/types.go:33:9: expected (unqualified)
identifier
[root@gohost ~]# rpm -qa |grep qpid-proton-c-devel
qpid-proton-c-devel-0.14.0-1.el6.x86_64
Ram
On Wed, Nov 2, 2016 at 10:27 AM, Alan Conway <ac...@redhat.com> wrote:
> On Tue, 2016-11-01 at 12:20 -0700, rammohan ganapavarapu wrote:
> > I have "qpid-proton-c-0.14.0-1.el6.x86_64" installed and my borker
> > version
> > is "qpid-cpp-server-1.35.0-2.el6.x86_64" so the proton-c rpm version
> > is not
> > right?
> >
>
> You need qpid-proton-c-devel RPM for the header files which are used to
> compile the Go binding. With that you should be able to
>
> go get qpid.apache.org/electron
>
> Note I updated it yesterday, so if it didn't work before, try again.
>
> > Ram
> >
> > On Thu, Oct 27, 2016 at 2:05 PM, Alan Conway <ac...@redhat.com>
> > wrote:
> >
> > >
> > > On Thu, 2016-10-27 at 10:16 -0700, rammohan ganapavarapu wrote:
> > > >
> > > > Alan,
> > > >
> > > > I was trying to use this one http://godoc.org/github.com/streadwa
> > > > y/am
> > > > qp
> > > >
> > > > but not sure if it will work with any qpid broker or not, i am
> > > > getting
> > > > "2016/10/27 04:09:48 Exception (501) Reason: "Exception (501)
> > > > Reason:
> > > > \"frame could not be parsed\"""
> > > >
> > >
> > > First, make sure your qpidd is built & configured to support AMQP
> > > 1.0.
> > > The go client doesn't speak the older 0-10 version that qpidd also
> > > uses, but qpidd has spoken AMQP 1.0 for a long time so that
> > > shouldn't
> > > be a problem.
> > >
> > > Second: The Go client is a wrapper for a C library, there may be a
> > > mismatch between the Go code and the proton-C library you have
> > > installed. I would suggest downloading the latest proton release
> > > from
> > >
> > > http://qpid.apache.org/proton/
> > >
> > > and use the matching C and Go code from the release. We will figure
> > > out
> > > a better story for managing that relationship but we haven't yet :(
> > >
> > > Otherwise if you have to work with some specific (reasonably
> > > recent)
> > > older released version of proton I can help you get it working.
> > >
> > > Please let me know how you get on - like I said I'd like to add a
> > > generic request-response pattern to the electron package.
> > >
> > > >
> > > > Thanks,
> > > > Ram
> > > >
> > > >
> > > > On Thu, Oct 27, 2016 at 7:42 AM, Alan Conway <ac...@redhat.com>
> > > > wrote:
> > > >
> > > > >
> > > > >
> > > > > On Wed, 2016-10-26 at 21:05 -0700, rammohan ganapavarapu wrote:
> > > > > >
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I am trying to write a qpid-stat tool in go, any one
> > > > > > attempted to
> > > > > > do
> > > > > > it, if
> > > > > > so can you please share your ideas? or if you have any
> > > > > > documents
> > > > > > on
> > > > > > how to
> > > > > > write please share.
> > > > > >
> > > > > > Thanks,
> > > > > > Ram
> > > > >
> > > > > For a Go client I recommend the qpid.apache.org/electron
> > > > > package
> > > > > which
> > > > > is part of the Proton project.
> > > > >
> > > > > https://github.com/apache/qpid-proton/tree/master/examples/go
> > > > >
> > > > > To work with the latest you should use the code from the proton
> > > > > repo
> > > > > rather than the `go get` version as it is still progressing
> > > > > rapidly.
> > > > >
> > > > > qpid-stat and the other qpid tools are based on the request-
> > > > > response
> > > > > message pattern: send a correctly-formatted QMF request message
> > > > > with
> > > > > correlation-id and then process the response message. There's a
> > > > > "canned" request-response pattern in python at:
> > > > >
> > > > > https://github.com/apache/qpid-proton/blob/master/proton-c/bind
> > > > > ings
> > > > > /pyt
> > > > > hon/proton/utils.py
> > > > >
> > > > > QMF messages are maps, so your main work will be to construct
> > > > > and
> > > > > interpret nested maps with the right names/values. Look at the
> > > > > qpid-
> > > > > stat sources and the qmf schemas here:
> > > > >
> > > > > /home/aconway/qpid-cpp/src/qpid/acl/management-schema.xml
> > > > > /home/aconway/qpid-cpp/src/qpid/broker/management-schema.xml
> > > > > /home/aconway/qpid-cpp/src/qpid/legacystore/management-
> > > > > schema.xml
> > > > > /home/aconway/qpid-cpp/src/qpid/ha/management-schema.xml
> > > > > /home/aconway/qpid-cpp/src/qpid/linearstore/management-
> > > > > schema.xml
> > > > >
> > > > > You are probably mostly/only interested in the broker schema.
> > > > >
> > > > > I am very interested in this as I worked on the Go binding and
> > > > > also
> > > > > on
> > > > > schema-driven management tools (in python) for qpid-dispatch. I
> > > > > would
> > > > > like to add a canned "request-response" pattern to the Go
> > > > > binding
> > > > > which
> > > > > would make your job easier, but I won't get to that in the
> > > > > immediate
> > > > > term so maybe you'll do it for me :) I'm happy to help with
> > > > > pointers
> > > > > and any problems you find in the Go binding.
> > > > >
> > > > > Cheers,
> > > > > Alan.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > -------------------------------------------------------------
> > > > > ----
> > > > > ----
> > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > > > For additional commands, e-mail: users-help@qpid.apache.org
> > > > >
> > > > >
> > >
> > >
> > > -----------------------------------------------------------------
> > > ----
> > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > For additional commands, e-mail: users-help@qpid.apache.org
> > >
> > >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: qpid monitoring tool in GO
Posted by rammohan ganapavarapu <ra...@gmail.com>.
ok, will try and let you know.
On Nov 2, 2016 10:27 AM, "Alan Conway" <ac...@redhat.com> wrote:
> On Tue, 2016-11-01 at 12:20 -0700, rammohan ganapavarapu wrote:
> > I have "qpid-proton-c-0.14.0-1.el6.x86_64" installed and my borker
> > version
> > is "qpid-cpp-server-1.35.0-2.el6.x86_64" so the proton-c rpm version
> > is not
> > right?
> >
>
> You need qpid-proton-c-devel RPM for the header files which are used to
> compile the Go binding. With that you should be able to
>
> go get qpid.apache.org/electron
>
> Note I updated it yesterday, so if it didn't work before, try again.
>
> > Ram
> >
> > On Thu, Oct 27, 2016 at 2:05 PM, Alan Conway <ac...@redhat.com>
> > wrote:
> >
> > >
> > > On Thu, 2016-10-27 at 10:16 -0700, rammohan ganapavarapu wrote:
> > > >
> > > > Alan,
> > > >
> > > > I was trying to use this one http://godoc.org/github.com/streadwa
> > > > y/am
> > > > qp
> > > >
> > > > but not sure if it will work with any qpid broker or not, i am
> > > > getting
> > > > "2016/10/27 04:09:48 Exception (501) Reason: "Exception (501)
> > > > Reason:
> > > > \"frame could not be parsed\"""
> > > >
> > >
> > > First, make sure your qpidd is built & configured to support AMQP
> > > 1.0.
> > > The go client doesn't speak the older 0-10 version that qpidd also
> > > uses, but qpidd has spoken AMQP 1.0 for a long time so that
> > > shouldn't
> > > be a problem.
> > >
> > > Second: The Go client is a wrapper for a C library, there may be a
> > > mismatch between the Go code and the proton-C library you have
> > > installed. I would suggest downloading the latest proton release
> > > from
> > >
> > > http://qpid.apache.org/proton/
> > >
> > > and use the matching C and Go code from the release. We will figure
> > > out
> > > a better story for managing that relationship but we haven't yet :(
> > >
> > > Otherwise if you have to work with some specific (reasonably
> > > recent)
> > > older released version of proton I can help you get it working.
> > >
> > > Please let me know how you get on - like I said I'd like to add a
> > > generic request-response pattern to the electron package.
> > >
> > > >
> > > > Thanks,
> > > > Ram
> > > >
> > > >
> > > > On Thu, Oct 27, 2016 at 7:42 AM, Alan Conway <ac...@redhat.com>
> > > > wrote:
> > > >
> > > > >
> > > > >
> > > > > On Wed, 2016-10-26 at 21:05 -0700, rammohan ganapavarapu wrote:
> > > > > >
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I am trying to write a qpid-stat tool in go, any one
> > > > > > attempted to
> > > > > > do
> > > > > > it, if
> > > > > > so can you please share your ideas? or if you have any
> > > > > > documents
> > > > > > on
> > > > > > how to
> > > > > > write please share.
> > > > > >
> > > > > > Thanks,
> > > > > > Ram
> > > > >
> > > > > For a Go client I recommend the qpid.apache.org/electron
> > > > > package
> > > > > which
> > > > > is part of the Proton project.
> > > > >
> > > > > https://github.com/apache/qpid-proton/tree/master/examples/go
> > > > >
> > > > > To work with the latest you should use the code from the proton
> > > > > repo
> > > > > rather than the `go get` version as it is still progressing
> > > > > rapidly.
> > > > >
> > > > > qpid-stat and the other qpid tools are based on the request-
> > > > > response
> > > > > message pattern: send a correctly-formatted QMF request message
> > > > > with
> > > > > correlation-id and then process the response message. There's a
> > > > > "canned" request-response pattern in python at:
> > > > >
> > > > > https://github.com/apache/qpid-proton/blob/master/proton-c/bind
> > > > > ings
> > > > > /pyt
> > > > > hon/proton/utils.py
> > > > >
> > > > > QMF messages are maps, so your main work will be to construct
> > > > > and
> > > > > interpret nested maps with the right names/values. Look at the
> > > > > qpid-
> > > > > stat sources and the qmf schemas here:
> > > > >
> > > > > /home/aconway/qpid-cpp/src/qpid/acl/management-schema.xml
> > > > > /home/aconway/qpid-cpp/src/qpid/broker/management-schema.xml
> > > > > /home/aconway/qpid-cpp/src/qpid/legacystore/management-
> > > > > schema.xml
> > > > > /home/aconway/qpid-cpp/src/qpid/ha/management-schema.xml
> > > > > /home/aconway/qpid-cpp/src/qpid/linearstore/management-
> > > > > schema.xml
> > > > >
> > > > > You are probably mostly/only interested in the broker schema.
> > > > >
> > > > > I am very interested in this as I worked on the Go binding and
> > > > > also
> > > > > on
> > > > > schema-driven management tools (in python) for qpid-dispatch. I
> > > > > would
> > > > > like to add a canned "request-response" pattern to the Go
> > > > > binding
> > > > > which
> > > > > would make your job easier, but I won't get to that in the
> > > > > immediate
> > > > > term so maybe you'll do it for me :) I'm happy to help with
> > > > > pointers
> > > > > and any problems you find in the Go binding.
> > > > >
> > > > > Cheers,
> > > > > Alan.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > -------------------------------------------------------------
> > > > > ----
> > > > > ----
> > > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > > > For additional commands, e-mail: users-help@qpid.apache.org
> > > > >
> > > > >
> > >
> > >
> > > -----------------------------------------------------------------
> > > ----
> > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > For additional commands, e-mail: users-help@qpid.apache.org
> > >
> > >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: qpid monitoring tool in GO
Posted by Alan Conway <ac...@redhat.com>.
On Tue, 2016-11-01 at 12:20 -0700, rammohan ganapavarapu wrote:
> I have "qpid-proton-c-0.14.0-1.el6.x86_64" installed and my borker
> version
> is "qpid-cpp-server-1.35.0-2.el6.x86_64" so the proton-c rpm version
> is not
> right?
>
You need qpid-proton-c-devel RPM for the header files which are used to
compile the Go binding. With that you should be able to�
� �go get qpid.apache.org/electron
Note I updated it yesterday, so if it didn't work before, try again.
> Ram
>
> On Thu, Oct 27, 2016 at 2:05 PM, Alan Conway <ac...@redhat.com>
> wrote:
>
> >
> > On Thu, 2016-10-27 at 10:16 -0700, rammohan ganapavarapu wrote:
> > >
> > > Alan,
> > >
> > > I was trying to use this one http://godoc.org/github.com/streadwa
> > > y/am
> > > qp
> > >
> > > but not sure if it will work with any qpid broker or not, i am
> > > getting
> > > "2016/10/27 04:09:48 Exception (501) Reason: "Exception (501)
> > > Reason:
> > > \"frame could not be parsed\"""
> > >
> >
> > First, make sure your qpidd is built & configured to support AMQP
> > 1.0.
> > The go client doesn't speak the older 0-10 version that qpidd also
> > uses, but qpidd has spoken AMQP 1.0 for a long time so that
> > shouldn't
> > be a problem.
> >
> > Second: The Go client is a wrapper for a C library, there may be a
> > mismatch between the Go code and the proton-C library you have
> > installed. I would suggest downloading the latest proton release
> > from
> >
> > � http://qpid.apache.org/proton/
> >
> > and use the matching C and Go code from the release. We will figure
> > out
> > a better story for managing that relationship but we haven't yet :(
> >
> > Otherwise if you have to work with some specific (reasonably
> > recent)
> > older released version of proton I can help you get it working.
> >
> > Please let me know how you get on - like I said I'd like to add a
> > generic request-response pattern to the electron package.
> >
> > >
> > > Thanks,
> > > Ram
> > >
> > >
> > > On Thu, Oct 27, 2016 at 7:42 AM, Alan Conway <ac...@redhat.com>
> > > wrote:
> > >
> > > >
> > > >
> > > > On Wed, 2016-10-26 at 21:05 -0700, rammohan ganapavarapu wrote:
> > > > >
> > > > >
> > > > > Hi,
> > > > >
> > > > > I am trying to write a qpid-stat tool in go, any one
> > > > > attempted to
> > > > > do
> > > > > it, if
> > > > > so can you please share your ideas? or if you have any
> > > > > documents
> > > > > on
> > > > > how to
> > > > > write please share.
> > > > >
> > > > > Thanks,
> > > > > Ram
> > > >
> > > > For a Go client I recommend the qpid.apache.org/electron
> > > > package
> > > > which
> > > > is part of the Proton project.
> > > >
> > > > https://github.com/apache/qpid-proton/tree/master/examples/go
> > > >
> > > > To work with the latest you should use the code from the proton
> > > > repo
> > > > rather than the `go get` version as it is still progressing
> > > > rapidly.
> > > >
> > > > qpid-stat and the other qpid tools are based on the request-
> > > > response
> > > > message pattern: send a correctly-formatted QMF request message
> > > > with
> > > > correlation-id and then process the response message. There's a
> > > > "canned" request-response pattern in python at:
> > > >
> > > > https://github.com/apache/qpid-proton/blob/master/proton-c/bind
> > > > ings
> > > > /pyt
> > > > hon/proton/utils.py
> > > >
> > > > QMF messages are maps, so your main work will be to construct
> > > > and
> > > > interpret nested maps with the right names/values. Look at the
> > > > qpid-
> > > > stat sources and the qmf schemas here:
> > > >
> > > > /home/aconway/qpid-cpp/src/qpid/acl/management-schema.xml
> > > > /home/aconway/qpid-cpp/src/qpid/broker/management-schema.xml
> > > > /home/aconway/qpid-cpp/src/qpid/legacystore/management-
> > > > schema.xml
> > > > /home/aconway/qpid-cpp/src/qpid/ha/management-schema.xml
> > > > /home/aconway/qpid-cpp/src/qpid/linearstore/management-
> > > > schema.xml
> > > >
> > > > You are probably mostly/only interested in the broker schema.
> > > >
> > > > I am very interested in this as I worked on the Go binding and
> > > > also
> > > > on
> > > > schema-driven management tools (in python) for qpid-dispatch. I
> > > > would
> > > > like to add a canned "request-response" pattern to the Go
> > > > binding
> > > > which
> > > > would make your job easier, but I won't get to that in the
> > > > immediate
> > > > term so maybe you'll do it for me :) I'm happy to help with
> > > > pointers
> > > > and any problems you find in the Go binding.
> > > >
> > > > Cheers,
> > > > Alan.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > -------------------------------------------------------------
> > > > ----
> > > > ----
> > > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > > For additional commands, e-mail: users-help@qpid.apache.org
> > > >
> > > >
> >
> >
> > -----------------------------------------------------------------
> > ----
> > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > For additional commands, e-mail: users-help@qpid.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org