JBoss AS 5 jboss.platform.mbeanserver is set but "JBoss AS JVM" not discovered

[Alan Evans]

I am using JBoss AS 5 and RHQ 4.2.0 and I am unable to get my agents
to discover the JBoss JVMs.

I am suspicious that it is because I have put
"jboss.platform.mbeanserver" in a properties file rather than in a -D
commandline option.

./run.sh takes a --properties command line which allows you to specify
jboss and other system properties without using a -D commandline
option.  One of my Java pet-peeves is that it takes a million
different properties all of which have really long names to do
anything in java.  Then you end up with 'ps aux' output that is
extremely unreadable.

So for JBoss anything I can put in a properties file I do!  From what
I can tell putting "jboss.platform.mbeanserver" in a properties file
and using --properties is a sufficient replacement for the -D option.
In jmx-console the java.lang is visible and we use another tool that
requires the jboss.platform.mbeanserver property that seems to work
fine.

Is there any reason that putting jboss.platform.mbeanserver in a
properties file instead of on the command line would prevent RHQ from
being able to discover that Boss was exposing information from the
JVM?

Regards,
-Alan

[Jay Shaughnessy]

Alan, I don't know of any reason.  As  a sanity check have you tried 
adding the property with -D to see if the JVM is discovered?  If that 
doesn't work then there may be a different issue.

On 11/30/2011 6:32 PM, Alan Evans wrote:
> I am using JBoss AS 5 and RHQ 4.2.0 and I am unable to get my agents
> to discover the JBoss JVMs.
>
> I am suspicious that it is because I have put
> "jboss.platform.mbeanserver" in a properties file rather than in a -D
> commandline option.
>
> ./run.sh takes a --properties command line which allows you to specify
> jboss and other system properties without using a -D commandline
> option.  One of my Java pet-peeves is that it takes a million
> different properties all of which have really long names to do
> anything in java.  Then you end up with 'ps aux' output that is
> extremely unreadable.
>
> So for JBoss anything I can put in a properties file I do!  From what
> I can tell putting "jboss.platform.mbeanserver" in a properties file
> and using --properties is a sufficient replacement for the -D option.
> In jmx-console the java.lang is visible and we use another tool that
> requires the jboss.platform.mbeanserver property that seems to work
> fine.
>
> Is there any reason that putting jboss.platform.mbeanserver in a
> properties file instead of on the command line would prevent RHQ from
> being able to discover that Boss was exposing information from the
> JVM?
>
> Regards,
> -Alan
> _______________________________________________
> rhq-users mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/rhq-users

[Alan Evans]

Jay,

This is my next step but these systems are pre-prod and while to you
and I that would suggest that we can stop/start them pretty much at
will the customer doesn't feel the same way.  In my own testing -D and
--properties have given me the same result BUT I have not been able to
test -D on the systems in question as its a pain to get a window to
restart.  Especially if the window is for "I think this might help but
I really don't know" :-/

I will post the results when I do get a chance tho.  Meanwhile I have
since started a forum topic at jboss.org asking if they have any
indication that -D and --properties would give different results in
this case.

The post is at: http://community.jboss.org/message/639207

Regards,
-Alan

On Thu, Dec 1, 2011 at 9:12 AM, Jay Shaughnessy  wrote:
> Alan, I don't know of any reason.  As  a sanity check have you tried
> adding the property with -D to see if the JVM is discovered?  If that
> doesn't work then there may be a different issue.
>
> On 11/30/2011 6:32 PM, Alan Evans wrote:
> > I am using JBoss AS 5 and RHQ 4.2.0 and I am unable to get my agents
> > to discover the JBoss JVMs.
> >
> > I am suspicious that it is because I have put
> > "jboss.platform.mbeanserver" in a properties file rather than in a -D
> > commandline option.
> >
> > ./run.sh takes a --properties command line which allows you to specify
> > jboss and other system properties without using a -D commandline
> > option.  One of my Java pet-peeves is that it takes a million
> > different properties all of which have really long names to do
> > anything in java.  Then you end up with 'ps aux' output that is
> > extremely unreadable.
> >
> > So for JBoss anything I can put in a properties file I do!  From what
> > I can tell putting "jboss.platform.mbeanserver" in a properties file
> > and using --properties is a sufficient replacement for the -D option.
> > In jmx-console the java.lang is visible and we use another tool that
> > requires the jboss.platform.mbeanserver property that seems to work
> > fine.
> >
> > Is there any reason that putting jboss.platform.mbeanserver in a
> > properties file instead of on the command line would prevent RHQ from
> > being able to discover that Boss was exposing information from the
> > JVM?
> >
> > Regards,
> > -Alan
> > _______________________________________________
> > rhq-users mailing list
> > [e-mail]
> > https://fedorahosted.org/mailman/listinfo/rhq-users
>
> rhq-users mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/rhq-users

[Heiko W.Rupp]

Am 01.12.2011 um 00:32 schrieb Alan Evans:
> So for JBoss anything I can put in a properties file I do!  From what
> I can tell putting "jboss.platform.mbeanserver" in a properties file
> and using --properties is a sufficient replacement for the -D option.
> In jmx-console the java.lang is visible and we use another tool that
> requires the jboss.platform.mbeanserver property that seems to work
> fine.

Did you check with jconsole that this is visible. Jmx-console is an
internal tool, so this has different semantics.

[Steve Millidge]

Is the JBoss.org or JBoss EAP as I believe there is a problem with the profile service in JBoss.org which prevents RHQ monitoring JBoss 5 community.

Steve Millidge
C2B2
Sent from my BlackBerry® wireless device

-----Original Message-----
From: Alan Evans 
Sender: [e-mail]
Date: Wed, 30 Nov 2011 18:32:51 
To: 
Reply-To: [e-mail]
Subject: JBoss AS 5 jboss.platform.mbeanserver is set but "JBoss AS JVM" not
    discovered

I am using JBoss AS 5 and RHQ 4.2.0 and I am unable to get my agents
to discover the JBoss JVMs.

I am suspicious that it is because I have put
"jboss.platform.mbeanserver" in a properties file rather than in a -D
commandline option.

./run.sh takes a --properties command line which allows you to specify
jboss and other system properties without using a -D commandline
option.  One of my Java pet-peeves is that it takes a million
different properties all of which have really long names to do
anything in java.  Then you end up with 'ps aux' output that is
extremely unreadable.

So for JBoss anything I can put in a properties file I do!  From what
I can tell putting "jboss.platform.mbeanserver" in a properties file
and using --properties is a sufficient replacement for the -D option.
In jmx-console the java.lang is visible and we use another tool that
requires the jboss.platform.mbeanserver property that seems to work
fine.

Is there any reason that putting jboss.platform.mbeanserver in a
properties file instead of on the command line would prevent RHQ from
being able to discover that Boss was exposing information from the
JVM?

Regards,
-Alan
_______________________________________________
rhq-users mailing list
[e-mail]
https://fedorahosted.org/mailman/listinfo/rhq-users

[Alan Evans]

Sorry, I should have been more clear.  It is JBoss EAP 5.1.0.

-Alan

On Thu, Dec 1, 2011 at 12:59 PM,   wrote:
> Is the JBoss.org or JBoss EAP as I believe there is a problem with the profile service in JBoss.org which prevents RHQ monitoring JBoss 5 community.
>
> Steve Millidge
> C2B2
> Sent from my BlackBerry® wireless device
>
> -----Original Message-----
> From: Alan Evans 
> Sender: [e-mail]
> Date: Wed, 30 Nov 2011 18:32:51
> To: 
> Reply-To: [e-mail]
> Subject: JBoss AS 5 jboss.platform.mbeanserver is set but "JBoss AS JVM" not
>        discovered
>
> I am using JBoss AS 5 and RHQ 4.2.0 and I am unable to get my agents
> to discover the JBoss JVMs.
>
> I am suspicious that it is because I have put
> "jboss.platform.mbeanserver" in a properties file rather than in a -D
> commandline option.
>
> ./run.sh takes a --properties command line which allows you to specify
> jboss and other system properties without using a -D commandline
> option.  One of my Java pet-peeves is that it takes a million
> different properties all of which have really long names to do
> anything in java.  Then you end up with 'ps aux' output that is
> extremely unreadable.
>
> So for JBoss anything I can put in a properties file I do!  From what
> I can tell putting "jboss.platform.mbeanserver" in a properties file
> and using --properties is a sufficient replacement for the -D option.
> In jmx-console the java.lang is visible and we use another tool that
> requires the jboss.platform.mbeanserver property that seems to work
> fine.
>
> Is there any reason that putting jboss.platform.mbeanserver in a
> properties file instead of on the command line would prevent RHQ from
> being able to discover that Boss was exposing information from the
> JVM?
>
> Regards,
> -Alan
> _______________________________________________
> rhq-users mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/rhq-users
> _______________________________________________
> rhq-users mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/rhq-users