GlassFish SNMP Monitoring
glassfish_snmp_monitoring
In this blog we will talk about SNMP
Monitoring feature of GlassFish Enterprise Manager. GlassFish
Enterprise Manager is part of
Sun
GlassFish Portfolio. SNMP
Monitoring feature of GlassFish Enterprise Manager enables monitoring
of
GlassFish
using SNMP clients. This feature exposes data specified by
standard-based
J2EE-MIB.
J2EE-MIB
is specified by
JSR 77: J2EETM Management.
SNMP Monitoring feature of GlassFish Enterprise Manager is delivered as
a patch,
140750–01
on
SunSolve.
To use this feature, download the patch from SunSolve and unzip it to
get the
__assnmp.war
file. You can then deploy this web module to the server
instance you would like to monitor. To deploy, you can use
asadmin tool or
GlassFish Admin Console.
For more information about the asadmin deploy command, see the
Sun
GlassFish Enterprise Server 2.1 Reference Manual . For more
information about the using Admin Console, refer to the
Sun
GlassFish Enterprise Server 2.1 Application Deployment Guide
or Admin Console in-line help.
You can choose to monitor Domain Administration Server (DAS) or
individual (clustered or stand-alone) server instances, directly. When
you monitor DAS, you get the complete view of the domain i.e you get
monitoring data for all the server instances in the domain including
DAS,
server.
Whether you choose to monitor DAS or individual server instance, the
steps are exactly the same.
- Deploy __assnmp.war
on the instance you want to monitor
- Use any SNMP client to monitor that instance on port 10161.
For example, using SNMP client, snmpwalk, you
can query server data as follows:
snmpwalk -c public -v 1 -m
./J2EE-MIB localhost:10161 J2EE-MIB::j2eeSrvTable
For
the complete list of available tables, refer to
"Tables Supported for SNMP Monitoring" section of
Sun
GlassFish
Enterprise Server version 2.1 SNMP Reference.
In the
above example, we are assuming
J2EE-MIB
available in the current folder. You can download
J2EE-MIB from
here.
snmpwalk comes
with Solaris and Linux operating systems by default. On the
Solaris operating system, the
snmpwalk
command is available in the
/usr/sfw/bin
directory.
10161
is the default port and can be overridden if needed. To override
default port, refer to "Configuring
GlassFish SNMP Monitoring" section of the
Sun GlassFish
Enterprise Server version 2.1 SNMP Reference.
For the complete example, demonstrating monitoring
of DAS as well as individual instances (clustered or
stand-alone), please refer to "Monitoring Clustered and Stand-Alone
Server Instances" section of
Sun
GlassFish
Enterprise Server version 2.1 SNMP Reference.
Some of the other blogs on SNMP monitoring feature of GlassFish
Enterprise Manager are-
Posted at
09:08AM Feb 10, 2009
by rajeshwar in Sun |
Did someone actually try this?
It crashed out of the box for me, on 3 different servers (all 2.1). I could fix it by removing a line in a xml file in the war archive.
But it caused a deadlock in the server when deployed with our ear application (after a reboot). For now, this is confirmed by a sun support engineer, who is working on it.
Posted by Yannick Majoros on September 14, 2009 at 02:05 AM PDT #
Looks like I hit the same issue, in my lab. Do we have a bugid and work around attached to it ?
Posted by Anand Varada on September 29, 2009 at 02:13 PM PDT #
Applied the latest glassfish patch (128647-13), that fixed the 'crash' issue. Above patch is for 'sparc', you have to download correct patch, for your architecture.
Posted by Anand Varada on October 09, 2009 at 06:57 AM PDT #