You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by lahiru gunathilake <gl...@gmail.com> on 2008/06/20 06:45:01 UTC
Re: Fortnight report (week 3-4)
Hi Marnie and Aidan,
- Started implementing list command.
- Now list command works with following options and following option
values
1. list -o queue : list all the queue objects currently in the
broker
2. list -o virtualhost : list all the virtualhost objects
3. list -o all : list all the mbeans and with all the
attributes
4. list -d : list all the domains in the broker
- After implementing those features I thought of giving somewhat
formatted output and did some coding inorder to get a nice output for these
previos commands.
- Change the code as Aidan last week by phone and that code is far more
better that the one
- I wrote earlier and Aidan thanks for pointing that out.
- As Marnie ask me several types of objects to display using list
command I tried to implement those features too.
1. These objects
2. Connection
3. Consumers
4. publishers
Issues
======
Since those objects are not listing in jconsole when we start the broker
and monitor without running any client I couldn't
write that code and check whether it's working or not.So that's why I
thought of going through the broker code and find some way of access those
information or change the broker code inorder to create those objects even
when it start in normal mode(without running any client) then I can monitor
them easily in jconsole and find some way to access those MBeans.Do you have
any idea of doing this that would be really great to finish the
implementation of the command list. And once we finish that I think if we
can ask QPID users to use them and suggest some more features to
implement(new commands or some more options to list command) in interactive
mode.And when they use this in with a real broker we'll be able to find some
bugs in the code and I'm happy to fix them too.
Any comments about my work for last two weeks.
Thanks in advance
Regards
Lahiru
On Fri, Jun 6, 2008 at 8:49 AM, lahiru gunathilake <gl...@gmail.com>
wrote:
> hi Marnie and Aiden,
>
> I'm writing the fortnight report in point form and I hope this will useful
> everybody to go through it
> easily.
>
> 1. Started coding for Gsoc in the first week and reused some of the code
> I wrote when I'm experimenting the project.
> 2.Wrote some more code for reading command when we give commands with
> arguments.(code to read options separately with option values)
> (ex: ./qpid-admin -h localhost -p 3434)
> 3.Found a library to support for the GNU ReadLine and start developing the
> CLI using that
> library.
> 4.Since I used some previously written JMX code I was able to connect to
> the remote broker
> once user give appropriate commands.
> 5. Designed a class diagram to include new commands to interactive mode,
> and implemented it and added two
> basic commands to the command line.(but didn't implemented the logic for
> those commands,when you type those
> commands it will just print some text)I spent sometime
> 6.Created ant build for the CLI and committed code for the repository
> created in google code project
> according to the advice given by Aiden.(Thanks Aiden for the help)
> 7. Started writing some test cases.
> 8. Now Implementing the business logic of following commands.
> list
> info
>
> I have some questions when i come to implementation of those commands and I
> hope to write them in to the
> thread we are discussing thing from the very beginning.
>
> Any comments about the way I gave you my fortnight report ? Is this too
> long/too short..?
>
> And any thoughts about my work I have done during first two weeks.
>
> Thanks
> Lahiru
>
>
Re: Fortnight report (week 3-4)
Posted by lahiru gunathilake <gl...@gmail.com>.
hi Aidan,
I'm working on pre-M3 branch and I couldn't find those Publisher and
consumer classes. Could you please tell me to which brach do I have to patch
from the following M2.
M1/ <https://svn.apache.org/repos/asf/incubator/qpid/branches/M1/>
M2/ <https://svn.apache.org/repos/asf/incubator/qpid/branches/M2/>
M2.0.0.0_patch/<https://svn.apache.org/repos/asf/incubator/qpid/branches/M2.0.0.0_patch/>
M2.1-release/<https://svn.apache.org/repos/asf/incubator/qpid/branches/M2.1-release/>
M2.1.1/ <https://svn.apache.org/repos/asf/incubator/qpid/branches/M2.1.1/>
M2.1.x/ <https://svn.apache.org/repos/asf/incubator/qpid/branches/M2.1.x/>
M2.x/ <https://svn.apache.org/repos/asf/incubator/qpid/branches/M2.x/> And
when we concern Publisher classes there are so many publisher classes in
several places. It's bit of confusing.
On Wed, Jun 25, 2008 at 3:14 PM, Aidan Skinner <ai...@apache.org> wrote:
> On Wed, Jun 25, 2008 at 9:07 AM, lahiru gunathilake <gl...@gmail.com>
> wrote:
>
> Hey, that's great work! I'm really pleased with the progress you're
> making and the way the code is structured. :)
>
> > Yep I think so. Could you please specify me what to be instrument. At the
> > moment I'm working on instrumenting Publisher object. What else you want
> ?
>
> Consumers and Connections (Sessions)
As I told you Session is already instrumented(with AMQProtocolSessionMBean
and AMQMinaProtocolSession classes) but when I'm trying to access using the
CLI I couldn't access it and even the Jconsole doesn't show that and I'm
looking in to that too.
Thanks
Lahiru
> would seem the two next to do to
> me. That would make a good handful of objects that you've got listing
> and info working for, so I would probably start thinking about output
> formatting and the like now.
>
> As an aside, would it be possible for you to add a jar target to your
> build.xml so we get a qpid-cli-$version.jar, and a release target that
> packages that jar, it's deps and the qpid-cli script into a tar.gz?
>
> Thanks,
>
> - Aidan
> --
> aim/y!:aidans42 g:aidan.skinner@gmail.com <g%...@gmail.com>
> http://aidan.skinner.me.uk/
> "We belong to nobody and nobody belongs to us. We don't even belong to
> each other."
>
Re: Fortnight report (week 3-4)
Posted by Aidan Skinner <ai...@apache.org>.
On Wed, Jun 25, 2008 at 9:07 AM, lahiru gunathilake <gl...@gmail.com> wrote:
Hey, that's great work! I'm really pleased with the progress you're
making and the way the code is structured. :)
> Yep I think so. Could you please specify me what to be instrument. At the
> moment I'm working on instrumenting Publisher object. What else you want ?
Consumers and Connections (Sessions) would seem the two next to do to
me. That would make a good handful of objects that you've got listing
and info working for, so I would probably start thinking about output
formatting and the like now.
As an aside, would it be possible for you to add a jar target to your
build.xml so we get a qpid-cli-$version.jar, and a release target that
packages that jar, it's deps and the qpid-cli script into a tar.gz?
Thanks,
- Aidan
--
aim/y!:aidans42 g:aidan.skinner@gmail.com
http://aidan.skinner.me.uk/
"We belong to nobody and nobody belongs to us. We don't even belong to
each other."
Re: Fortnight report (week 3-4)
Posted by lahiru gunathilake <gl...@gmail.com>.
hi Aidan,
First thanks for the reply and I was waiting for a reply.
On Tue, Jun 24, 2008 at 8:30 PM, Aidan Skinner <ai...@apache.org> wrote:
> On Tue, Jun 24, 2008 at 5:35 AM, lahiru gunathilake <gl...@gmail.com>
> wrote:
>
> > I have gone through the qpid code last couple of days and able to
> understand
> > the management code.If I am suppose to instrument some more objects which
> > haven't already instrumented Now I'm in a possition to implement those
> > things in Qpid code but I have no idea how should I do that. Do I have to
> do
> > the modification and raise a Jira and attach the patch or what should I
> > do(at the moment I'm working on M3 ).
>
> Raise a Jira and attach the patch, remember to click the grant box and
> I'll review and commit ASAP.
>
> > > If I can't think like that there are some objects which are registered
> in
> > > the code but that code doesn't execute when normal server start
> happens. (Am
> > > I correct ?) So could you please tell me how should I run that
> particular
> > > code.
> >
> > In here I'm talking about the AMQProtocolSessionMBean class which is
> > instrumented but not shown in the jconsole. If somebody can answer that
> > would be really useful for me.
>
> You should be able to get at them through the managed object registry.
> I'm not sure why JConsole isn't showing them, they use the register()
> method in DefaultManagedObject to get themselves in there. Are they
> accessable through the VirtualHost once the connection has been
> established?
Yep I think so. Could you please specify me what to be instrument. At the
moment I'm working on instrumenting Publisher object. What else you want ?
Regards
Lahiru
>
>
> - Aidan
> --
> aim/y!:aidans42 g:aidan.skinner@gmail.com <g%...@gmail.com>
> http://aidan.skinner.me.uk/
> "We belong to nobody and nobody belongs to us. We don't even belong to
> each other."
>
Re: Fortnight report (week 3-4)
Posted by Aidan Skinner <ai...@apache.org>.
On Tue, Jun 24, 2008 at 5:35 AM, lahiru gunathilake <gl...@gmail.com> wrote:
> I have gone through the qpid code last couple of days and able to understand
> the management code.If I am suppose to instrument some more objects which
> haven't already instrumented Now I'm in a possition to implement those
> things in Qpid code but I have no idea how should I do that. Do I have to do
> the modification and raise a Jira and attach the patch or what should I
> do(at the moment I'm working on M3 ).
Raise a Jira and attach the patch, remember to click the grant box and
I'll review and commit ASAP.
> > If I can't think like that there are some objects which are registered in
> > the code but that code doesn't execute when normal server start happens. (Am
> > I correct ?) So could you please tell me how should I run that particular
> > code.
>
> In here I'm talking about the AMQProtocolSessionMBean class which is
> instrumented but not shown in the jconsole. If somebody can answer that
> would be really useful for me.
You should be able to get at them through the managed object registry.
I'm not sure why JConsole isn't showing them, they use the register()
method in DefaultManagedObject to get themselves in there. Are they
accessable through the VirtualHost once the connection has been
established?
- Aidan
--
aim/y!:aidans42 g:aidan.skinner@gmail.com
http://aidan.skinner.me.uk/
"We belong to nobody and nobody belongs to us. We don't even belong to
each other."
Re: Fortnight report (week 3-4)
Posted by lahiru gunathilake <gl...@gmail.com>.
Hi Marnie and Aidan,
I have gone through the qpid code last couple of days and able to understand
the management code.If I am suppose to instrument some more objects which
haven't already instrumented Now I'm in a possition to implement those
things in Qpid code but I have no idea how should I do that. Do I have to do
the modification and raise a Jira and attach the patch or what should I
do(at the moment I'm working on M3 ).
Now list command supports to all the objects types it has instrumented other
than ProtocolSession.
Still I have to following problem can anyone answer my question please .....
:-)
On Sat, Jun 21, 2008 at 12:42 PM, lahiru gunathilake <gl...@gmail.com>
wrote:
> hi Marnie and Aidan,
>
> On Sat, Jun 21, 2008 at 1:38 AM, Marnie McCormack <
> marnie.mccormack@googlemail.com> wrote:
>
>> Hi Lahiru,
>>
>> Thanks for your status report - very useful.
>>
>> Firstly, I think your progress is good and I've been pleased with the way
>> in
>> which you're approaching your project & resolving the issues you
>> encounter.
>> Well done !
>>
>> I think your proposal to add extra mbean methods to expose the various
>> objects you've noted (from my suggestions - noted below) is a good one.
>>
>> Aidan & I discussed a two step progression from where you are now (good
>> foundation for the CLI structure, existing properties listable) to a more
>> functionally rich (useful for users) app.
>>
>> Step 1 would be to add the extra attributes for listing information.
>
> Yep I'm in this position right now. I think you are talking about allowing
> some more object types to list with -o argument.
> As an example -o Connection, -o Consumer, -o Publisher. But as I told you
> earlier I'm bit of confuse with this since I couldn't monitor this with
> jconsole and i have no idea on how to query for those objects and I have few
> questions to ask regarding this and if somebody can answer for these
> questions I will be able to understand what's going on inside the broker.
>
> If I can't monitor those information(previously mentioned objects) using
> jconsole when I start the broker can I think those objects are not
> registered in the MBean server ? So I can try to expose them in the broker
> code and write a query to extract those objects in the CLI.
>
> If I can't think like that there are some objects which are registered in
> the code but that code doesn't execute when normal server start happens. (Am
> I correct ?) So could you please tell me how should I run that particular
> code.
>
In here I'm talking about the AMQProtocolSessionMBean class which is
instrumented but not shown in the jconsole. If somebody can answer that
would be really useful for me.
Thanks in advance
Regards
Lahiru
>
>
> when marnie telling me that consumers, publishers, connection have to
> monitor using list command what does that really mean when I search for
> publisher objects using grep command there are lot of publisher classes so
> could you please tell me what sought of objects do I have to support for the
> more specificly. As an example AMQQueue object is managed using JMX so
> likewise what else you want to manage.
>
> At the moment what I'm doing is reading the broker code and trying to
> understand how you are exposing your classes using MBeans. Inorder to start
> this first step I need some feed from you......
>
> Waiting for a reply hopefully
>
> Thanks in advanced
> Regards
> Lahiru
>
>> Step 2
>> is to identify & expose the management objects and allow them to be
>> managed
>> i.e. figure out between us what users might want to do from the CLI in the
>> way of management including killing connections etc. Some of this is there
>> already, and available via the console - other bits will be new.
>>
>> So, for example - the ability to kill a connection is probably there and
>> to
>> remove a message (possibly only from the front of the q) but it'd be good
>> to
>> be able to do more sophisticated things like dump a message to a file or
>> display the selectors in use on a q etc. We can discuss this in more
>> detail
>> and specify it (within the time available) over the next week.
>>
>> Finally, just to re-iterate - keep up the good work !
>>
>> Bfn,
>> Marnie
>>
>>
>> On 6/20/08, lahiru gunathilake <gl...@gmail.com> wrote:
>> >
>> > Hi Marnie and Aidan,
>> >
>> >
>> >
>> > - Started implementing list command.
>> >
>> >
>> > - Now list command works with following options and following option
>> > values
>> >
>> >
>> >
>> > 1. list -o queue : list all the queue objects currently in
>> the
>> > broker
>> > 2. list -o virtualhost : list all the virtualhost objects
>> > 3. list -o all : list all the mbeans and with all the
>> > attributes
>> > 4. list -d : list all the domains in the broker
>> >
>> >
>> >
>> > - After implementing those features I thought of giving somewhat
>> > formatted output and did some coding inorder to get a nice output for
>> > these
>> > previos commands.
>> >
>> >
>> >
>> > - Change the code as Aidan last week by phone and that code is far
>> more
>> > better that the one
>> > - I wrote earlier and Aidan thanks for pointing that out.
>> >
>> >
>> >
>> > - As Marnie ask me several types of objects to display using list
>> > command I tried to implement those features too.
>> >
>> >
>> > 1. These objects
>> > 2. Connection
>> > 3. Consumers
>> > 4. publishers
>> >
>> >
>> > Issues
>> > ======
>> > Since those objects are not listing in jconsole when we start the broker
>> > and monitor without running any client I couldn't
>> > write that code and check whether it's working or not.So that's why I
>> > thought of going through the broker code and find some way of access
>> those
>> > information or change the broker code inorder to create those objects
>> even
>> > when it start in normal mode(without running any client) then I can
>> monitor
>> > them easily in jconsole and find some way to access those MBeans.Do you
>> > have
>> > any idea of doing this that would be really great to finish the
>> > implementation of the command list. And once we finish that I think if
>> we
>> > can ask QPID users to use them and suggest some more features to
>> > implement(new commands or some more options to list command) in
>> interactive
>> > mode.And when they use this in with a real broker we'll be able to find
>> > some
>> > bugs in the code and I'm happy to fix them too.
>> >
>> > Any comments about my work for last two weeks.
>> >
>> > Thanks in advance
>> > Regards
>> > Lahiru
>> >
>> > On Fri, Jun 6, 2008 at 8:49 AM, lahiru gunathilake <gl...@gmail.com>
>> > wrote:
>> >
>> > > hi Marnie and Aiden,
>> > >
>> > > I'm writing the fortnight report in point form and I hope this will
>> > useful
>> > > everybody to go through it
>> > > easily.
>> > >
>> > > 1. Started coding for Gsoc in the first week and reused some of the
>> code
>> > > I wrote when I'm experimenting the project.
>> > > 2.Wrote some more code for reading command when we give commands with
>> > > arguments.(code to read options separately with option values)
>> > > (ex: ./qpid-admin -h localhost -p 3434)
>> > > 3.Found a library to support for the GNU ReadLine and start developing
>> > the
>> > > CLI using that
>> > > library.
>> > > 4.Since I used some previously written JMX code I was able to connect
>> to
>> > > the remote broker
>> > > once user give appropriate commands.
>> > > 5. Designed a class diagram to include new commands to interactive
>> mode,
>> > > and implemented it and added two
>> > > basic commands to the command line.(but didn't implemented the logic
>> for
>> > > those commands,when you type those
>> > > commands it will just print some text)I spent sometime
>> > > 6.Created ant build for the CLI and committed code for the repository
>> > > created in google code project
>> > > according to the advice given by Aiden.(Thanks Aiden for the help)
>> > > 7. Started writing some test cases.
>> > > 8. Now Implementing the business logic of following commands.
>> > > list
>> > > info
>> > >
>> > > I have some questions when i come to implementation of those commands
>> and
>> > I
>> > > hope to write them in to the
>> > > thread we are discussing thing from the very beginning.
>> > >
>> > > Any comments about the way I gave you my fortnight report ? Is this
>> too
>> > > long/too short..?
>> > >
>> > > And any thoughts about my work I have done during first two weeks.
>> > >
>> > > Thanks
>> > > Lahiru
>> > >
>> > >
>> >
>>
>
>
Re: Fortnight report (week 3-4)
Posted by lahiru gunathilake <gl...@gmail.com>.
hi Marnie and Aidan,
On Sat, Jun 21, 2008 at 1:38 AM, Marnie McCormack <
marnie.mccormack@googlemail.com> wrote:
> Hi Lahiru,
>
> Thanks for your status report - very useful.
>
> Firstly, I think your progress is good and I've been pleased with the way
> in
> which you're approaching your project & resolving the issues you encounter.
> Well done !
>
> I think your proposal to add extra mbean methods to expose the various
> objects you've noted (from my suggestions - noted below) is a good one.
>
> Aidan & I discussed a two step progression from where you are now (good
> foundation for the CLI structure, existing properties listable) to a more
> functionally rich (useful for users) app.
>
> Step 1 would be to add the extra attributes for listing information.
Yep I'm in this position right now. I think you are talking about allowing
some more object types to list with -o argument.
As an example -o Connection, -o Consumer, -o Publisher. But as I told you
earlier I'm bit of confuse with this since I couldn't monitor this with
jconsole and i have no idea on how to query for those objects and I have few
questions to ask regarding this and if somebody can answer for these
questions I will be able to understand what's going on inside the broker.
If I can't monitor those information(previously mentioned objects) using
jconsole when I start the broker can I think those objects are not
registered in the MBean server ? So I can try to expose them in the broker
code and write a query to extract those objects in the CLI.
If I can't think like that there are some objects which are registered in
the code but that code doesn't execute when normal server start happens. (Am
I correct ?) So could you please tell me how should I run that particular
code.
when marnie telling me that consumers, publishers, connection have to
monitor using list command what does that really mean when I search for
publisher objects using grep command there are lot of publisher classes so
could you please tell me what sought of objects do I have to support for the
more specificly. As an example AMQQueue object is managed using JMX so
likewise what else you want to manage.
At the moment what I'm doing is reading the broker code and trying to
understand how you are exposing your classes using MBeans. Inorder to start
this first step I need some feed from you......
Waiting for a reply hopefully
Thanks in advanced
Regards
Lahiru
> Step 2
> is to identify & expose the management objects and allow them to be managed
> i.e. figure out between us what users might want to do from the CLI in the
> way of management including killing connections etc. Some of this is there
> already, and available via the console - other bits will be new.
>
> So, for example - the ability to kill a connection is probably there and to
> remove a message (possibly only from the front of the q) but it'd be good
> to
> be able to do more sophisticated things like dump a message to a file or
> display the selectors in use on a q etc. We can discuss this in more detail
> and specify it (within the time available) over the next week.
>
> Finally, just to re-iterate - keep up the good work !
>
> Bfn,
> Marnie
>
>
> On 6/20/08, lahiru gunathilake <gl...@gmail.com> wrote:
> >
> > Hi Marnie and Aidan,
> >
> >
> >
> > - Started implementing list command.
> >
> >
> > - Now list command works with following options and following option
> > values
> >
> >
> >
> > 1. list -o queue : list all the queue objects currently in
> the
> > broker
> > 2. list -o virtualhost : list all the virtualhost objects
> > 3. list -o all : list all the mbeans and with all the
> > attributes
> > 4. list -d : list all the domains in the broker
> >
> >
> >
> > - After implementing those features I thought of giving somewhat
> > formatted output and did some coding inorder to get a nice output for
> > these
> > previos commands.
> >
> >
> >
> > - Change the code as Aidan last week by phone and that code is far more
> > better that the one
> > - I wrote earlier and Aidan thanks for pointing that out.
> >
> >
> >
> > - As Marnie ask me several types of objects to display using list
> > command I tried to implement those features too.
> >
> >
> > 1. These objects
> > 2. Connection
> > 3. Consumers
> > 4. publishers
> >
> >
> > Issues
> > ======
> > Since those objects are not listing in jconsole when we start the broker
> > and monitor without running any client I couldn't
> > write that code and check whether it's working or not.So that's why I
> > thought of going through the broker code and find some way of access
> those
> > information or change the broker code inorder to create those objects
> even
> > when it start in normal mode(without running any client) then I can
> monitor
> > them easily in jconsole and find some way to access those MBeans.Do you
> > have
> > any idea of doing this that would be really great to finish the
> > implementation of the command list. And once we finish that I think if we
> > can ask QPID users to use them and suggest some more features to
> > implement(new commands or some more options to list command) in
> interactive
> > mode.And when they use this in with a real broker we'll be able to find
> > some
> > bugs in the code and I'm happy to fix them too.
> >
> > Any comments about my work for last two weeks.
> >
> > Thanks in advance
> > Regards
> > Lahiru
> >
> > On Fri, Jun 6, 2008 at 8:49 AM, lahiru gunathilake <gl...@gmail.com>
> > wrote:
> >
> > > hi Marnie and Aiden,
> > >
> > > I'm writing the fortnight report in point form and I hope this will
> > useful
> > > everybody to go through it
> > > easily.
> > >
> > > 1. Started coding for Gsoc in the first week and reused some of the
> code
> > > I wrote when I'm experimenting the project.
> > > 2.Wrote some more code for reading command when we give commands with
> > > arguments.(code to read options separately with option values)
> > > (ex: ./qpid-admin -h localhost -p 3434)
> > > 3.Found a library to support for the GNU ReadLine and start developing
> > the
> > > CLI using that
> > > library.
> > > 4.Since I used some previously written JMX code I was able to connect
> to
> > > the remote broker
> > > once user give appropriate commands.
> > > 5. Designed a class diagram to include new commands to interactive
> mode,
> > > and implemented it and added two
> > > basic commands to the command line.(but didn't implemented the logic
> for
> > > those commands,when you type those
> > > commands it will just print some text)I spent sometime
> > > 6.Created ant build for the CLI and committed code for the repository
> > > created in google code project
> > > according to the advice given by Aiden.(Thanks Aiden for the help)
> > > 7. Started writing some test cases.
> > > 8. Now Implementing the business logic of following commands.
> > > list
> > > info
> > >
> > > I have some questions when i come to implementation of those commands
> and
> > I
> > > hope to write them in to the
> > > thread we are discussing thing from the very beginning.
> > >
> > > Any comments about the way I gave you my fortnight report ? Is this too
> > > long/too short..?
> > >
> > > And any thoughts about my work I have done during first two weeks.
> > >
> > > Thanks
> > > Lahiru
> > >
> > >
> >
>
Re: Fortnight report (week 3-4)
Posted by Marnie McCormack <ma...@googlemail.com>.
Hi Lahiru,
Thanks for your status report - very useful.
Firstly, I think your progress is good and I've been pleased with the way in
which you're approaching your project & resolving the issues you encounter.
Well done !
I think your proposal to add extra mbean methods to expose the various
objects you've noted (from my suggestions - noted below) is a good one.
Aidan & I discussed a two step progression from where you are now (good
foundation for the CLI structure, existing properties listable) to a more
functionally rich (useful for users) app.
Step 1 would be to add the extra attributes for listing information. Step 2
is to identify & expose the management objects and allow them to be managed
i.e. figure out between us what users might want to do from the CLI in the
way of management including killing connections etc. Some of this is there
already, and available via the console - other bits will be new.
So, for example - the ability to kill a connection is probably there and to
remove a message (possibly only from the front of the q) but it'd be good to
be able to do more sophisticated things like dump a message to a file or
display the selectors in use on a q etc. We can discuss this in more detail
and specify it (within the time available) over the next week.
Finally, just to re-iterate - keep up the good work !
Bfn,
Marnie
On 6/20/08, lahiru gunathilake <gl...@gmail.com> wrote:
>
> Hi Marnie and Aidan,
>
>
>
> - Started implementing list command.
>
>
> - Now list command works with following options and following option
> values
>
>
>
> 1. list -o queue : list all the queue objects currently in the
> broker
> 2. list -o virtualhost : list all the virtualhost objects
> 3. list -o all : list all the mbeans and with all the
> attributes
> 4. list -d : list all the domains in the broker
>
>
>
> - After implementing those features I thought of giving somewhat
> formatted output and did some coding inorder to get a nice output for
> these
> previos commands.
>
>
>
> - Change the code as Aidan last week by phone and that code is far more
> better that the one
> - I wrote earlier and Aidan thanks for pointing that out.
>
>
>
> - As Marnie ask me several types of objects to display using list
> command I tried to implement those features too.
>
>
> 1. These objects
> 2. Connection
> 3. Consumers
> 4. publishers
>
>
> Issues
> ======
> Since those objects are not listing in jconsole when we start the broker
> and monitor without running any client I couldn't
> write that code and check whether it's working or not.So that's why I
> thought of going through the broker code and find some way of access those
> information or change the broker code inorder to create those objects even
> when it start in normal mode(without running any client) then I can monitor
> them easily in jconsole and find some way to access those MBeans.Do you
> have
> any idea of doing this that would be really great to finish the
> implementation of the command list. And once we finish that I think if we
> can ask QPID users to use them and suggest some more features to
> implement(new commands or some more options to list command) in interactive
> mode.And when they use this in with a real broker we'll be able to find
> some
> bugs in the code and I'm happy to fix them too.
>
> Any comments about my work for last two weeks.
>
> Thanks in advance
> Regards
> Lahiru
>
> On Fri, Jun 6, 2008 at 8:49 AM, lahiru gunathilake <gl...@gmail.com>
> wrote:
>
> > hi Marnie and Aiden,
> >
> > I'm writing the fortnight report in point form and I hope this will
> useful
> > everybody to go through it
> > easily.
> >
> > 1. Started coding for Gsoc in the first week and reused some of the code
> > I wrote when I'm experimenting the project.
> > 2.Wrote some more code for reading command when we give commands with
> > arguments.(code to read options separately with option values)
> > (ex: ./qpid-admin -h localhost -p 3434)
> > 3.Found a library to support for the GNU ReadLine and start developing
> the
> > CLI using that
> > library.
> > 4.Since I used some previously written JMX code I was able to connect to
> > the remote broker
> > once user give appropriate commands.
> > 5. Designed a class diagram to include new commands to interactive mode,
> > and implemented it and added two
> > basic commands to the command line.(but didn't implemented the logic for
> > those commands,when you type those
> > commands it will just print some text)I spent sometime
> > 6.Created ant build for the CLI and committed code for the repository
> > created in google code project
> > according to the advice given by Aiden.(Thanks Aiden for the help)
> > 7. Started writing some test cases.
> > 8. Now Implementing the business logic of following commands.
> > list
> > info
> >
> > I have some questions when i come to implementation of those commands and
> I
> > hope to write them in to the
> > thread we are discussing thing from the very beginning.
> >
> > Any comments about the way I gave you my fortnight report ? Is this too
> > long/too short..?
> >
> > And any thoughts about my work I have done during first two weeks.
> >
> > Thanks
> > Lahiru
> >
> >
>