For 3.0, you need to:
boot amx, (use the bootAMX operation on amx-support->boot-amx)
turn on monitoring to via the admin gui... set the level to HIGH (LOW is
a no-op in 3.0)
hth,
vbk
glassfish_at_javadesktop.org wrote:
> Hello.
> I have a simple application that uses GlassFish 2 Monitoring beans. At first I'm turning on monitoring level via web admin console in section Configuration->Monitoring(HIGH or LOW).
> Then when I want to see for example JDBC connection pools state I requested for beans names
> "amx:j2eeType=X-JDBCConnectionPoolMonitor,name=*
> and then get attribute "NumConnUsed" in each of them.
> The same stat I`v got for other Monitors for example HTTPListenerMonitor
>
> Now I want to upgrade my application to work with GlassFish 3.
> I expected that amx path to monitor beans have been changed.
> So I turned on Monitoring in GlassFish3 then made a query for all beans names
> and then I`ve got the only Monitoring Bean with such path
> pp=/domain/configs/config[server-config],type=monitoring-service
> that contains attributes "level"
> but there was no JDBCConnectionPoolMonitor or HTTPListenerMonitor and a lot of Monitor beans within any path,
>
> So please, can anyone say where and how can be obtained Monitor data in Glassfish3 as it was accessible in Glassfish2?
> [Message sent by forum member 'jmichaelj']
>
> http://forums.java.net/jive/thread.jspa?messageID=477186
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>