+1 also here, I'm using JConsole extensivly
2008/5/5 Yoav Shapira <[EMAIL PROTECTED]>:
> On Sun, May 4, 2008 at 11:49 PM, Costin Manolache <[EMAIL PROTECTED]> wrote:
> > If you don't add the option - you'll see that tomcat uses a separate mbean
> > server. I want to have it consistent -
> >
On Sun, May 4, 2008 at 11:49 PM, Costin Manolache <[EMAIL PROTECTED]> wrote:
> If you don't add the option - you'll see that tomcat uses a separate mbean
> server. I want to have it consistent -
> with or without -Dcom.sun... to use the platform mbean server.
+1 from me. Maybe add a flag to di
I think that's doing the same thing - loading the platform mbean server
early on.
If you don't add the option - you'll see that tomcat uses a separate mbean
server. I want to have it consistent -
with or without -Dcom.sun... to use the platform mbean server.
Costin
On Sun, May 4, 2008 at 8:40 P
I guess I'm doing something "funny" then because I see a *lot* of Tomcat
MBeans in jconsole.
I added -Dcom.sun.management.jmxremote, of course -- to cover Java 5 and
left it in place for Java 6, but otherwise I don't think I did anything
funny until within my web app.
Costin Manolache wrote:
This is a proposal for a very small change in tomcat trunk, to make tomcat
easier to use with JConsole.
Right now if you start tomcat 'out of box' and than try to inspect it with
jconsole, you'll only see the 'platform' mbeans
(memory etc). That's because tomcat doesn't use the platform mbean serve
