This exception does not have an impact on the filter: the initialisation
of the filter and of the webapp continues after this exception.
It does not have either any impact on the other filters in the chain.
The impact of this exception could be:
- values will not be collected anymore for graphics after the exception
and certainly until the restart of the server
- statistics of the requests for the day, week, month and year periods
(except the "all" period) will not be updated anymore until the restart
of the server
- the reports will not contain any graphics
or if you dot not see such behavior then there is no impact.
The problem is related to the fact that the class
org.jrobin.core.RrdNioBackend has a java.util.Timer defined as static
final. This timer is correctly canceled by the destroy method of the
javamelody filter, in order to stop the thread of the timer, and of
course this timer instance can't be used anymore after being canceled.
It is my understanding that classes (and so this timer instance) should
be discarded and reloaded by the classloader of the webapp when the
webapp is undeployed and then reinitialized. I may be wrong, except that
it seems to work in Tomcat 6.0.
Do you see the impact as said above?
Which version of jetty do you use?
Which JDK and version do you use?
Have you put the jrobin-1.5.9.1.jar file in the WEB-INF/lib directory of
the webapp or somewhere else?
And the jrobin-1.5.9.1.jar file is not in the classpath (-cp or
-classpath option) of the JVM?
Do you use either the debug mode of the JVM or jrebel?
And have you any ideas on this?
bye, Emeric
Le 14/09/2010 15:57, Toby a �crit :