More info. I was looking at both - 4.0.3 and 4.0.4-B1 - and I found out the following difference in the code: - when calling webappclassloader, 'modified' method, it checks for the modified date of the jar/class by calling resources.getAttributes - looking at the ProxyDirContext ( getAttributes method ), I found a difference. ----> 4.0.3: it does a cacheLookup and return an entry; ----> 4.0.4-B1: it always returns a null. So it tries to open the File which doesn't exist because of the relative path that is used and says the resource is missing. This change has something related to new code that releases DirContext in StandarContext ? Thanks PS. How can I disable Webappclassloader from keep checking every minute for changes in my webapp ? ( it's messes up with debugging :)) ). Renato <[EMAIL PROTECTED]> wrote: Hi,
I have an application that uses the rowset.jar from Sun. When I use the manager application in Tomcat 4.0.3 it works ok. I'm able to stop and start the context that is using it. Although when I load this application on 4.0.4-B1 and try to stop the context I get the message: WebappClassLoader: Resource '/WEB-INF/lib/rowset.jar' is missing And when I start the context, it fails: FAIL - Application at context path /examples could not be startedFAIL - Encountered exception java.lang.IllegalStateException: standardHost.start /examples: LifecycleException: Loader has already been started I can test any patch. Thanks Renato - Brazil. --------------------------------- Do You Yahoo!? Yahoo! Sports - live college hoops coverage --------------------------------- Do You Yahoo!? Yahoo! Sports - live college hoops coverage
