Good point Dain. That is a important consideration.
I think it might be difficult to fully integrate the jmx-explorer with
the admin console now given that it has been written without portlets.
Perhaps we should consider some type of loose integration where it can
still function independently from the admin console when necessary.
My main motivation for integrating this capability was to provide
one-stop shopping for Geronimo admins.
Joe
Dain Sundstrom wrote:
My concern is about being able to debug/manage a server when the web
console is having problems. If we could use the remote JConsole to
debug the server, then I would not be concerned. Unfortunately, it
doesn't run (GERONIMO-1329). If someone fixed that, I see no reason to
keep these features separate.
-dain
On Feb 24, 2006, at 8:33 AM, Joe Bohn wrote:
I proposed that a while ago and at the time there were strong
opinions that it should remain independent. Perhaps opinions have
changed. I especially think this would be the way to go if we also
introduce role based views of the admin console.
Let's see what others think ... perhaps the winds have changed.
Joe
Paul McMahan wrote:
Joe, I took a look at the jmxexplorer as well and agree that it is a
very useful tool (impressive work, Simon!). In fact, I would like
throw out a suggestion that we incorporate this utility, or some
derivation of it, into the admin console. What do others think about
doing that? If there are no objections then I'm happy to contribute
the time/effort to make this happen.
Best wishes,
Paul
On 2/23/06, Joe Bohn <[EMAIL PROTECTED]> wrote:
I was able to get the jmx-explorer working with some tweaks and some
offline conversations with Simon. It does show this information for
the currently running assembly and the set of configurations it
includes
(although there were some oddities that Simon is checking into). It
would be good if we could get this updated utility live sometime.
However, it still might be valuable to see this in totality (at
least it
was for me when making changes that affect all of the assemblies) with
the parents of all configurations and not just those for a particular
assembly. It's also nice to have it in a graphical form. But
there is
certainly *a lot* to be said for getting live information and not
maintaining another representation.
If nobody else finds this useful I'll just continue to use it myself.
Joe
Simon Godik wrote:
Joe Bohn wrote:
I'm not sure if these charts are helpful for anybody else or
not. It's
a point in time snapshot that I created of parent (import)
dependencies
between configurations at the moment (which some of the changes
that I
have pending to clean up some dependencies).
The first page has the server configuration imports and the
second page
includes the client and "childless" configs (configs not
referenced as
parents by any other configuration).
If you think it's useful then I will try to find a location where
we can
keep this ... but I suspect it would get out of date fairly quickly.
Joe
In my long lost jmx explorer (still attached to some jira) I have
configuration tree that shows these relationships
Simon
--
Joe Bohn
joe.bohn at earthlink.net
"He is no fool who gives what he cannot keep, to gain what he cannot
lose." -- Jim Elliot
--
Joe Bohn
joe.bohn at earthlink.net
"He is no fool who gives what he cannot keep, to gain what he cannot
lose." -- Jim Elliot
--
Joe Bohn
joe.bohn at earthlink.net
"He is no fool who gives what he cannot keep, to gain what he cannot
lose." -- Jim Elliot
