I sporadically get this exception in the logs:
WEB0133: Failed to read attribute count5xx from MBean
com.sun.appserv:type=GlobalRequestProcessor,name=htt
p8181
javax.management.InstanceNotFoundException: This operation failed,
because it could not be handled by this domain.
An example of such an operation is creating application server
instances or clusters when they are not supported by the given domain.
The actual error is: MBean instance not found:
com.sun.appserv:type=GlobalRequestProcessor,name=http8181
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.manufactureAndRegisterMBean(SunoneInterceptor.java:663)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.registerWithPersistenceCheck(SunoneInterceptor.java:692)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.getAttribute(SunoneInterceptor.java:315)
at com.sun.enterprise.interceptor.DynamicInterceptor.getAttribute(DynamicInterceptor.java:192)
at com.sun.enterprise.web.stats.StatsUtil.getStatistic(StatsUtil.java:71)
at com.sun.enterprise.web.stats.HTTPListenerStatsImpl.getCount5xxLong(HTTPListenerStatsImpl.java:496)
at com.sun.enterprise.web.stats.PWCRequestStatsImpl.getCount5xx(PWCRequestStatsImpl.java:349)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
.... lots more ....
It is always some "Failed to read attribute" error but the name of the
attribute varies, like count5xx or maxSpareThreadsStats, count302,
count403, requestCount or something like that. What is the reason for
these tracebacks? Is it a known bug in Glassfish v2?
--
mvh Björn