RE: Webapp Classpath Loading

When I turn logging to 'all' for everything, all I see is this:
(grepping for Error and Exception)

 

 [11:28:38.202] AbstractParser: com.caucho.xml.RemoteURLException: URL
`http://java.sun.com/j2ee/dtds/web-app_2_2.dtd' was not opened because
it is a remote URL.  Any URL scheme other than file: must be handled by
a custom entity resolver.

[11:28:38.323] ServletConfigImpl:
javax.management.NotCompliantMBeanException:
resin:type=Servlet,Server=default,Host=default,WebApp=/journey,name=resi
n-jsp mbean has no MBean interface

[11:28:38.324] ServletConfigImpl:
javax.management.NotCompliantMBeanException:
resin:type=Servlet,Server=default,Host=default,WebApp=/journey,name=resi
n-jspx mbean has no MBean interface

[11:28:39.130] ServletConfigImpl: java.lang.NoClassDefFoundError:
com/ihg/dec/framework/commons/utils/logging/DbgLoggerFactory 

[11:28:39.136] ServletManager: javax.servlet.ServletException:
com/ihg/dec/framework/commons/utils/logging/DbgLoggerFactory

[11:28:39.141] Application: javax.servlet.ServletException:
com/ihg/dec/framework/commons/utils/logging/DbgLoggerFactory

 

Would the first three errors cause a problem?  I know that the missing
class is present in a jar file in <webapp-dir>/WEB-INF/lib, which is
specified in the app-default.xml, like I mentioned in the previous
email.  I also have the serve.root class-loader specified in the
resin.conf:

 

  <server>

    <!-- adds all .jar files under the resin/lib directory -->

    <class-loader>

      <tree-loader path="${resin.home}/lib"/>

      <tree-loader path="${server.root}/lib"/>

    </class-loader>

    ...

  </server>

 

I wouldn't think that it's anything specific to the classes themselves,
as developers are able to run locally without seeing this issue.

 

-Bryan

________________________________

From: [email protected]
[mailto:[email protected]] On Behalf Of Scott Ferguson
Sent: Thursday, May 25, 2006 2:32 PM
To: [email protected]
Subject: Re: Webapp Classpath Loading

 

 

On May 25, 2006, at 11:30 AM, Choate, Bryan (IHG) wrote:





Scott-

 

I checked into that, but in resin-pro-3.0.18/conf/app-default.xml I see
this:

 

This would appear to be what we're looking for, but neither the library
jars nor the application classes are being loaded (at least as of the
time that the webapp's web.xml file is parsed).  Do I need to define
something specific in the resin.conf for each webapp?

 

No, although you might want to turn on full logging.

 

The JDK sometimes reports ClassNotFound when the class exists, but has
some kind of error.  For example, if a superclass or a component class
was missing, the JDK can return ClassNotFound instead of a more useful
exception type. (e.g. if you have classes in ${server.root}/lib, but no
class-loader for it).  So you might look at the component classes.

 

- Scott