From: Jennifer Chou <jennifer.chou_at_oracle.com>
Date: Thu, 11 Aug 2011 13:13:05 -0400

For the different garbage collectors, I noticed that the DAS uses
http://localhost:4848/monitoring/domain/server/jvm/garbage-collectors/MarkSweepCompact

and the clustered instance uses
http://localhost:4848/monitoring/domain/i1/jvm/garbage-collectors/PS%20MarkSweep

The DAS uses -client and the instance runs with -server.
For the instance, I see 'current : Java HotSpot(TM) Server VM'
http://localhost:4848/monitoring/domain/i1/jvm/runtime/vmname-current

and the DAS I see 'current : Java HotSpot(TM) Client VM'
http://localhost:4848/monitoring/domain/server/jvm/runtime/vmname-current

I haven't seen the misspelled 'commitednonheapsize-count'. If you have
a way to reproduce this it would be helpful.

HTH,
Jennifer

On 8/11/2011 6:55 AM, forums_at_java.net wrote:
> Hi
>
> We have a bunch of OSS Glassfish 3.x servers mostly running in clustered
> setups and for some reason one (or possibly more) servers have different
> names for certain items when accessing it through the REST monitoring
> interface. For instance, on most servers we have
> "/monitoring/domain/<instance-name>/jvm/garbage-collectors/PS%20MarkSweep"
>
> while on others we have
> "/monitoring/domain/<instance-name>/jvm/garbage-collectors/MarkSweepCompact".
>
> Also in the JVM memory section we have "committednonheapsize-count" vs
> "commitednonheapsize-count" (notice the difference in spelling). All
> servers
> run the same OS and patches as well as java version so I'm a bit lost
> where
> to start looking for the cause of this.
>
> //Johan
>
>
> --
>
> [Message sent by forum member 'calcifer']
>
> View Post: http://forums.java.net/node/831306
>
>