Hi Marnie, Here's the console view...
Regards lahiru On Tue, May 6, 2008 at 11:25 PM, lahiru gunathilake <[EMAIL PROTECTED]> wrote: > Hi Marnie, > > I was able to connect to Qpid Java broker JMX MBean server using JMX > connector and print all the org.apache.qpid domain resource (Only the object > names) which are exposed using JMX. Since this is a simple stage of my > project and I just sending you a screanshot of the out put of my program(I > think no need to waste your time by sending the source). > I think now we can have a discussion on how to give user options and all > of the other implementation details. And at last, one question, when I got > all the domains after connecting to Qpid server I saw there are some other > domains like Implementation, > sun.com.management,java.lang,java.util.logging(you can see that in the > screanshot) and do you want me to extract those informations too? > > Thanks in advance > > Regards > lahiru > > > On Mon, May 5, 2008 at 10:04 AM, lahiru gunathilake <[EMAIL PROTECTED]> > wrote: > > > Hi Marnie, > > > > previous mail was sent accidentally, sorry for the inconvenience please > > be kind enough to go through this email. > > > > > > > As you told me I started of finding all the exposed JMX attributes and > > > appropriate operations and I'm listing them down in this email. In that > > > I'm > > > listing only the corresponding class name and corresponding MBean but > > > there > > > are intermediate classes in between those two. Each and ever MBean class > > > is > > > extending AMQManagedObject class as you said. > > > > > > > > > MBEAN CLASS NAME RELAVENT INTERFACE > > > > =================== ==================== > > > > > > > > 1. AMQUserManagementMBean UserManagement > > > 2. AMQBrokerMangerMBean ManagedBroker > > > 3. AMQQMBean ManagedQueue > > > 4. ExchangeMBean ManagedExchange > > > > > > > Although there are only four classes when we run the qpid-server it > > create number of instances of these classes with different object names and > > register them in the MBean server so there are lot of information to extract > > through a JMX connector. Specially there are some more complex code lying in > > the Queueing layer. > > If I have made a mistake in this could you please tell me and honestly > > that will be very useful for me and still I'm going through the code and > > meanwhile I'm trying to run the management console too. Hope that will be > > helpful to understand the project more solid way. As the next step I will go > > through the code of JMX instrumentation in Qpid and try to understand how > > management console works. > > > > I need some feed from any of you on what to do next, and according to my > > point as the next step I can write some sample code which connect with the > > MBeanServer and do some play with the information as the initial step of the > > CLI. > > > > Any thoughts please...? > > > > Thanks in advace > > > > Regs > > lahiru > > > > > > > > > > > > > > > > > On Sun, May 4, 2008 at 7:12 PM, lahiru gunathilake <[EMAIL PROTECTED]> > > > wrote: > > > > > > > Hi marnie, > > > > > > > > Thanks for the reply first. > > > > Honestly me too was unable to work a lot on Gsoc last couple of days > > > > due to my personal work and I've already started on reading the JMX > > > > MBeans > > > > code of Qpid and your reply probably will be very helpful for me. I > > > > thought > > > > of reading about JMX stuff and other thing for few days and I hope I > > > > will > > > > be able to get a good understanding about the project ASAP. > > > > If you want to have a chat with me just let me know at what time I > > > > should login. > > > > > > > > Thanks in advance > > > > > > > > Regs > > > > lahiru > > > > > > > > On Sun, May 4, 2008 at 4:15 PM, Marnie McCormack < > > > > [EMAIL PROTECTED]> wrote: > > > > > > > > > Hi Lahiru, > > > > > > > > > > Here's an email I prepared on Wed evening but didn't get a chance > > > > > to send - > > > > > I hope it helps with your query on the codebase/mbeans. I'm out of > > > > > the > > > > > office this week for personal reasons, but I'll try to login as I > > > > > can and > > > > > keep up to date with your progress. > > > > > > > > > > Re your question on mid evaluation, why don't we discuss that when > > > > > we next > > > > > talk. I'd hope I'll be able to call you later this week, but I'll > > > > > confirm by > > > > > email to you. Apologies for the slight blip in communication, it > > > > > should be > > > > > very temporary. > > > > > > > > > > Hth .... > > > > > > > > > > > > > > > Hi Lahiru, > > > > > > > > > > > > > > > As a starting point, you should have a look at the > > > > > AMQManagedObject > > > > > interface which is implemented by all classes exposing management > > > > > methods/attributes. If you search for derived classes > > > > > (implementing classes) > > > > > you'll see the set of entities which provide attributes for JMX > > > > > calls. > > > > > > > > > > In particular, the ManagedQueue interface in package > > > > > org.apache.qpid.server.queue contains a substantial amount of the > > > > > exposed > > > > > attributes. This is where the attributes exposed on the broker's > > > > > queues are > > > > > described. AMQQueueMBean (same package) implements this interface. > > > > > This is > > > > > the best place to get a handle on the queue attributes exposed via > > > > > JMX. > > > > > > > > > > I think a useful first step would be to list out the elements > > > > > provided via > > > > > JMX on the broker, and note where they are implemented in the > > > > > code. The > > > > > usage of the various elements will differ, in terms of the > > > > > frequency with > > > > > which a user might want to check them etc. I hope this would be a > > > > > useful > > > > > start ! We can then discuss whether the detail I sent previously > > > > > about the > > > > > parameters for running the CLI scripts are appropriate. > > > > > > > > > > The management console sholdn't inform much of what your doing, in > > > > > terms of > > > > > being a template. However, it might make it easier for you to > > > > > understand the > > > > > various elements provided. Martin & Aidan should be able to help > > > > > you get it > > > > > up & running. Martin/Aidan - can you can help Lahiru with this > > > > > please ? > > > > > Thanks ! > > > > > > > > > > Senaka's emails on the console setup help a little, though > > > > > possibly not so > > > > > relevant to a windows env ? > > > > > > > > > > Hth, > > > > > Regards, > > > > > Marnie > > > > > > > > > > > > > > > > > > > > On 5/3/08, lahiru gunathilake <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > hi Martin and Marnie, > > > > > > > > > > > > Yep I'm going through that code. I found a location where you > > > > > have written > > > > > > MBeans and i want to know is that the only location you have > > > > > registered or > > > > > > do you have several other places too. > > > > > > This is the place > > > > > > > > > > > > > > > > > https://svn.apache.org/repos/asf/incubator/qpid/trunk/qpid/java/broker/src/main/java/org/apache/qpid/server/management > > > > > > > > > > > > I will keep on looking if you know some other places please let > > > > > me know > > > > > > that will be helpful for me to get a rough understanding about > > > > > Qpid JMX > > > > > > interface. > > > > > > > > > > > > Thanks > > > > > > lahiru > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, May 2, 2008 at 6:11 PM, Martin Ritchie < > > > > > [EMAIL PROTECTED]> > > > > > > wrote: > > > > > > > > > > > > > Hi, Marnie is away for a few days she may respond but just in > > > > > case > > > > > > > here are my thoughts so you are not held up over the weekend. > > > > > > > > > > > > > > On 01/05/2008, lahiru gunathilake <[EMAIL PROTECTED]> wrote: > > > > > > > > Hi, > > > > > > > > > > > > > > > > First I'm very sorry for taking sometime to reply to your > > > > > mail( > > > > > > because > > > > > > > I > > > > > > > > was uable to be online for yesterday) and thanks a lot for > > > > > writing me > > > > > > > about > > > > > > > > the Gsoc project. > > > > > > > > Thats great and now I know, the image I had about the > > > > > project is > > > > > > > correct. I > > > > > > > > think I have to create a project plane(I realize it after > > > > > having a > > > > > > chat > > > > > > > with > > > > > > > > Aidan) and once I create it I will send it to you. > > > > > > > > > > > > > > > > In order to create a clear project plan honestly could you > > > > > please > > > > > > tell > > > > > > > me > > > > > > > > what should I finish when it comes to mid evaluation. I'm > > > > > sure, that > > > > > > > will > > > > > > > > help me a lot to create a better road map. > > > > > > > > > > > > > > > > Next thing.. Could you please look in to my inline comment. > > > > > > > > > > > > > > > > > > > > > > > > On Wed, Apr 30, 2008 at 12:13 AM, Marnie McCormack < > > > > > > > > [EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > > > Hi Lahiru, > > > > > > > > > > > > > > > > > > As promised here are my thoughts about what I'd like to > > > > > achieve > > > > > > from > > > > > > > the > > > > > > > > > project I defined for your GSoC work. > > > > > > > > > > > > > > > > > > So, currently we provide some JMX calls which expose > > > > > various > > > > > > > attributes in > > > > > > > > > the Qpid Java broker. We have users who are interested in > > > > > these > > > > > > > > > attributes, > > > > > > > > > but there's currently no simple way for them to get > > > > > access to them. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Can I know exactly what are they(where are those attributes > > > > > in the > > > > > > Qpid > > > > > > > code > > > > > > > > base) . I can check them with Jconsole as a user. But as a > > > > > developer > > > > > > > can I > > > > > > > > know where that code located and where is the code where > > > > > it expose > > > > > > as > > > > > > > JMX > > > > > > > > calls. (Honestly if this is a task which shoud be done by > > > > > my self > > > > > > just > > > > > > > give > > > > > > > > me a clue and I will find where are those ) > > > > > > > > > > > > > > Have a look for all the MBean classes these are the bits that > > > > > show up > > > > > > > in JConsole. > > > > > > > > > > > > > > > > > > > > > > > > They can > > > > > > > > > view them on the management console (assuming they can > > > > > get it > > > > > > working > > > > > > > :-), > > > > > > > > > they can attach some other monitoring GUI or proprietary > > > > > > application. > > > > > > > > > > > > > > > > > > For some of our JMX props, they can be set up to log > > > > > alerts to the > > > > > > > broker > > > > > > > > > log - which can again be monitored. > > > > > > > > > > > > > > > > > > However, it would be really useful if they could simply > > > > > use a CLI > > > > > > > tool to > > > > > > > > > extract the information they're looking for. > > > > > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > > > > I had envisaged it taking a really simple form: > > > > > > > > > > > > > > > > > > - a shell script (bash or .bat) to call the CLI tool, > > > > > probably > > > > > > > simply > > > > > > > > > wrapping a java call, which will run as a daemon (or > > > > > service) > > > > > > > > > - a config/properties file or command line options to > > > > > specify: > > > > > > > > > - the JMX attribute to extract > > > > > > > > > - the frequency with which to extract it, in minutes > > > > > (i.e. an > > > > > > > > > elapsed time between extraction like 5 minutes) > > > > > > > > > > > > > > > > > > > > > > > > If the time is five minutes then if the deamon runs one hour > > > > > the CLI > > > > > > > outputs > > > > > > > > around 12 out put information. > > > > > > > > As an example CLI should write 12 out put files to a give > > > > > location. > > > > > > Am > > > > > > > I > > > > > > > > correct .. ? > > > > > > > > > > > > > > I would say it would write 12 times to single file that has > > > > > been > > > > > > > specified. > > > > > > > Potentially you could configure various logging information to > > > > > go to a > > > > > > > variety of files, but I'd start with a single configurable > > > > > file. > > > > > > > > > > > > > > > > > > > > > > > > > - a path into which to record the output > > > > > > > > > - an option for the output format (see my proposal > > > > > info about > > > > > > > > > formatting etc) like csv, tab-delimited, html etc. > > > > > This might > > > > > > be > > > > > > > > > better done > > > > > > > > > > > > > > > > > > > > > > > > Can be done..! > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > as optional export into another tool ? > > > > > > > > > > > > > > > > > > > > > > > > > > - the properties/config should be extensible so that > > > > > new > > > > > > attributes > > > > > > > > > implemented in the broker can easily be added > > > > > > > > > > > > > > > > > Sure.. this should be in that way. > > > > > > > > > > > > > > > > > So, when a user wants to get useful management information > > > > > from the > > > > > > > broker > > > > > > > > > (but not using a GUI) they can simply create a props file > > > > > and voila > > > > > > ! > > > > > > > > > > > > > > > > > > > > > > > > Not much clear this statement. "create props file and > > > > > voila!" > > > > > > > > > > > > > > I think what Marnie is saying is that what would be good is > > > > > for a user > > > > > > > to specify a property file that contains the information they > > > > > are > > > > > > > after so when they run the command line tool it will simply > > > > > return > > > > > > > that. If they wished that property file could be used by the > > > > > daemon > > > > > > > process to populate the logfile. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > What do you think ? Does this make sense to you ok ? > > > > > > > > > > > > > > > > > > > > > > > > Exactly this is the best description I got about my project > > > > > and thanks > > > > > > a > > > > > > > lot > > > > > > > > for your great assist. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I'll reply to your email about issues shortly, in a > > > > > separate email. > > > > > > > > > > > > > > > > > > Hth, > > > > > > > > > Thanks & Regards, > > > > > > > > > Marnie > > > > > > > > > > > > > > > > > > > > > > > > > Thanks in advance > > > > > > > > > > > > > > > > Regs > > > > > > > > > > > > > > > > lahiru > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Martin Ritchie > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > East or West > > > > > > Mahindians are the > > > > > > Best... ! > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > East or West > > > > Mahindians are the > > > > Best... ! > > > > > > > > > > > > > > > > -- > > > East or West > > > Mahindians are the > > > Best... ! > > > > > > > > > > > -- > > East or West > > Mahindians are the > > Best... ! > > > > > > -- > East or West > Mahindians are the > Best... ! > -- East or West Mahindians are the Best... !
