Hi,
We are using jetty-monitor to print the thread usage, which following the
configurations on the link [1]. After running the jetty server for a while, we
found that tons of EventState instances, which were held by the _states
variable in the AttrEventTrigger. We are trying to dive into the monitor the
codes, it seems that the issue is that, the thread status retrieved from the
mbean server are saved in the _states map in the match method, but there is no
remove action is invoked. So is it possible an issue here ?
Although the jetty version we used is an very old one 7.6.7, it seems that
no code is changed in the lastest 9.x version.
publicfinalbooleanmatch(longtimestamp)
throwsException
{
MBeanServerConnection serverConnection = JMXMonitor.getServiceConnection();
TYPE value = null;
try
{
intpos = this._attributeName.indexOf('.');
if(pos < 0) {
value = (Comparable)serverConnection.getAttribute(this._nameObject,
this._attributeName);
} else{
value =
getValue((CompositeData)serverConnection.getAttribute(this._nameObject,
this._attributeName.substring(0, pos)), this._attributeName
.substring(pos + 1));
}
}
catch(Exception ex)
{
LOG.debug(ex);
}
booleanresult = false;
if(value != null)
{
result = match(value);
if((result) || (getSaveAll())) {
this._states.put(Long.valueOf(timestamp), newEventState(
getID(), getNameString(), value));
}
}
returnresult;
}
[1]
https://wiki.eclipse.org/Jetty/Reference/jetty-monitor#Starting_the_In-process_Monitor_______________________________________________
jetty-users mailing list
jetty-users@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jetty-users
