Periodic stack trace in tomcat logs 'java.lang.IllegalStateException: The resources may not be accessed if they are not currently started'

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Unpack tomcat 8.0.5
2. configure maven with
        <dependency>
                <groupId>net.bull.javamelody</groupId>
                <artifactId>javamelody-core</artifactId>
                <version>1.51.0</version>
        </dependency>
3. Every 60 seconds I see in logs:

WARN : 13:53:21,192 [javamelody          ] bull.javamelody:warn:45 - exception 
while collecting data
java.lang.IllegalStateException: The resources may not be accessed if they are 
not currently started
        at org.apache.catalina.webresources.StandardRoot.validate(StandardRoot.java:232)
        at org.apache.catalina.webresources.StandardRoot.listWebAppPaths(StandardRoot.java:142)
        at org.apache.catalina.core.ApplicationContext.getResourcePaths(ApplicationContext.java:588)
        at org.apache.catalina.core.ApplicationContextFacade.getResourcePaths(ApplicationContextFacade.java:178)
        at net.bull.javamelody.JavaInformations.buildDependenciesList(JavaInformations.java:427)
        at net.bull.javamelody.JavaInformations.<init>(JavaInformations.java:163)
        at net.bull.javamelody.Collector.collectLocalContextWithoutErrors(Collector.java:292)
        at net.bull.javamelody.FilterContext$CollectTimerTask.run(FilterContext.java:56)
        at java.util.TimerThread.mainLoop(Timer.java:555)
        at java.util.TimerThread.run(Timer.java:505)

I run under linux, centos,
java version "1.7.0_55"
Java(TM) SE Runtime Environment (build 1.7.0_55-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.55-b03, mixed mode)

Original issue reported on code.google.com by jjaku...@gmail.com on 16 Jun 2014 at 11:58

[GoogleCodeExporter]

I do not reproduce your issue after downloading tomcat 8.0.5 and using a 
test-webapp with jdk 1.7. I do not question the fact that you have an exception 
at some point in time.
But, can you give more precise steps, than just "configure maven with 
[javamelody dependency...]" to reproduce the issue?

For example, can you give here the zip file of a simple webapp project (using 
maven if possible) to reproduce the issue?

Original comment by evernat@free.fr on 24 Jun 2014 at 10:36

[GoogleCodeExporter]

Anyway, after thinking about cases, I have fixed that. It's committed in trunk 
(revision 3827) and ready for the next release (1.52).

Original comment by evernat@free.fr on 4 Jul 2014 at 2:57

• Changed state: Fixed

[GoogleCodeExporter]

Sorry I didn't send zip with simple webapp, but I had this in production 
application which I couldn't send. I was still thinking about preparing 
something small, but cause of small spare time I didn't manage to do it. The 
worst torture was for me thinking all this time, that maybe it was fault of my 
app not javamelody, and I made a fake issue. BTW, the same app with javamelody 
is working fine in wildfly8. 

Original comment by jjaku...@gmail.com on 11 Jul 2014 at 9:55