Jetty

Managing a large number of contexts in JMX is difficult

Details

  • Type: Improvement Improvement
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 6.1.2rc3
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    1

Description

Contexts appear in tools such as jconsole identified by a number starting from 0. If you have more than a couple of contexts, it is difficult to identify a context when it needs to be managed, because you have to view the Attributes of each to find the one you want.

Attached is an implementation of org.mortbay.jetty.servlet.management.ContextMBean, which will use the context path as the id, rather than a sequential number.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Greg Wilkins added a comment -

Stephen,

Jetty used to have the context path as part of the object name, however we changed for the reason that
context path is part of the configuration of a context and may be changed at runtime.
This gives you the dilemma of changing the object name or not!

The advice we were given is that proper management consoles would be able to provide proper
displays with context path taken from the object values rather than the name.

So while it IS a pain to only have numeric values... there is good reason.

I guess we could consider an option of naming with context path?

Show
Greg Wilkins added a comment - Stephen, Jetty used to have the context path as part of the object name, however we changed for the reason that context path is part of the configuration of a context and may be changed at runtime. This gives you the dilemma of changing the object name or not! The advice we were given is that proper management consoles would be able to provide proper displays with context path taken from the object values rather than the name. So while it IS a pain to only have numeric values... there is good reason. I guess we could consider an option of naming with context path?
Hide
Permalink
Stephen Stevens added a comment -

Greg,

I have used the context path as a shortcut (at that point in time) to the source location of the application. I just wanted to have a meaningful name, and the fact that it is the context path is not really what I had in mind - I just needed something (mostly) unique and meaningful. My main concern is with webapps, so I could have created a WebAppContextMBean and used the WAR attribute, but then I would have had to deal with different type of URLs and parse out the parent directory details. So I elected to use the context path (which is effectively the source location at the creation of the bean), and store it so that it would remain constant.

I don't WANT the object name to reflect the current value of context path. That would defeat the entire purpose (in my case at least) because they would mostly be updated to /, and that doesn't identify them at all, unless you then go and arbitrarily select one of the virtual host names as a prefix.

Whilst I understand your comment that jconsole might not be a "proper" tool, it does what I want (and has the right price . Do you know of a similarly priced console that allows you to specify an attribute value to be displayed in place of the ObjectName id in the management tree?

Thanks for your feedback.

Show
Stephen Stevens added a comment - Greg, I have used the context path as a shortcut (at that point in time) to the source location of the application. I just wanted to have a meaningful name, and the fact that it is the context path is not really what I had in mind - I just needed something (mostly) unique and meaningful. My main concern is with webapps, so I could have created a WebAppContextMBean and used the WAR attribute, but then I would have had to deal with different type of URLs and parse out the parent directory details. So I elected to use the context path (which is effectively the source location at the creation of the bean), and store it so that it would remain constant. I don't WANT the object name to reflect the current value of context path. That would defeat the entire purpose (in my case at least) because they would mostly be updated to /, and that doesn't identify them at all, unless you then go and arbitrarily select one of the virtual host names as a prefix. Whilst I understand your comment that jconsole might not be a "proper" tool, it does what I want (and has the right price . Do you know of a similarly priced console that allows you to specify an attribute value to be displayed in place of the ObjectName id in the management tree? Thanks for your feedback.
Hide
Permalink
Greg Wilkins added a comment -

OK, I have added a getObjectNameBasis to ObjectMBean, if it returns a name
then the object name is type=blah,name=name,id=0

So you can now see context displaynames (or the last component of the location path)
and servlet/filter names as well.

cheers

Show
Greg Wilkins added a comment - OK, I have added a getObjectNameBasis to ObjectMBean, if it returns a name then the object name is type=blah,name=name,id=0 So you can now see context displaynames (or the last component of the location path) and servlet/filter names as well. cheers

People

  • Assignee:
    Unassigned
    Reporter:
    Stephen Stevens
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: