"null"s in tomcat logs

[Manavendra Gupta <ma...@bsil.com>]

Hi,

I had posted a similar message (on the datasource thread) a few days ago, but I guess it was lost in the flurry of "I don't understand the objective of this list" messages.

Below is a snippet of the tomcat 4.1 logs on my NT workstation. Notice there are two "null" entries... while, both the filter as well as the DataSource work. My tomcat 4.1 setup on RHL 7.3 box shows me the nulls too, but the DataSource doesn't work there (no, I'm not trying to mix two topics together).

Anybody got any idea why there is this null entry in the log messages?

<log-entry>
XmlMapper: org.apache.catalina.core.StandardContext.setPublicId(-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN)
XmlMapper: org.apache.catalina.core.StandardContext.setDisplayName( Real Time Image Billing System)
XmlMapper: org.apache.catalina.core.StandardContext.addParameter( webmaster,manav@bsil.com)
XmlMapper: new null org.apache.catalina.deploy.FilterDef filter FilterDef[filterName=null, filterClass=null]
XmlMapper: org.apache.catalina.deploy.FilterMap.setFilterName( RTIFilter)
XmlMapper: org.apache.catalina.deploy.FilterMap.setURLPattern( *.do)
XmlMapper: Calling org.apache.catalina.core.StandardContext.addFilterMap FilterMap[filterName=RTIFilter, urlPattern=*.do]
XmlMapper: pop filter-mapping org.apache.catalina.deploy.FilterMap: FilterMap[filterName=RTIFilter, urlPattern=*.do]
XmlMapper: org.apache.catalina.core.StandardContext.addApplicationListener( com.bsil.mx.TomcatTestListener)
XmlMapper: new org.apache.catalina.core.StandardWrapperXmlMapper: org.apache.catalina.core.StandardWrapper.setName( FrontController)
XmlMapper: org.apache.catalina.core.StandardWrapper.setServletClass( com.bsil.rti.controller.FrontController)
XmlMapper: org.apache.catalina.core.StandardWrapper.addInitParameter( mappingPath, /WEB-INF)
XmlMapper: org.apache.catalina.core.StandardWrapper.addInitParameter( mappingFile, mappings.xml)
XmlMapper: org.apache.catalina.core.StandardWrapper.setLoadOnStartupString( 5)
XmlMapper: Calling org.apache.catalina.core.StandardContext.addChild StandardWrapper[FrontController]
XmlMapper: pop org.apache.catalina.core.StandardWrapper
XmlMapper: org.apache.catalina.core.StandardContext.addServletMapping( *.do, FrontController)
XmlMapper: org.apache.catalina.core.StandardContext.setSessionTimeout( 30)
XmlMapper: new null org.apache.catalina.deploy.ContextResource resource-ref ContextResource[name=null, scope=Shareable]
XmlMapper: org.apache.catalina.deploy.ContextResource.setDescription( Oracle Datasource example)
XmlMapper: org.apache.catalina.deploy.ContextResource.setName( jdbc/myoracle)
XmlMapper: org.apache.catalina.deploy.ContextResource.setType( javax.sql.DataSource)
XmlMapper: org.apache.catalina.deploy.ContextResource.setAuth( Container)
XmlMapper: Calling org.apache.catalina.core.StandardContext.addResource ContextResource[name=jdbc/myoracle, description=Oracle Datasource example, type=javax.sql.DataSource, auth=Container, scope=Shareable]
XmlMapper: pop resource-ref org.apache.catalina.deploy.ContextResource: ContextResource[name=jdbc/myoracle, description=Oracle Datasource example, type=javax.sql.DataSource, auth=Container, scope=Shareable]
</log-entry>

Regards,
manav.

Re: "null"s in tomcat logs

["Craig R. McClanahan" <cr...@apache.org>]

On Fri, 13 Dec 2002, Manavendra Gupta wrote:

> Date: Fri, 13 Dec 2002 08:01:09 +0530
> From: Manavendra Gupta <ma...@bsil.com>
> Reply-To: Tomcat Users List <to...@jakarta.apache.org>,
>      Manavendra Gupta <ma...@bsil.com>
> To: Tomcat Users List <to...@jakarta.apache.org>
> Subject: "null"s in tomcat logs
>
> Hi,
>
> I had posted a similar message (on the datasource thread) a few days ago, but I guess it was lost in the flurry of "I don't understand the objective of this list" messages.
>
> Below is a snippet of the tomcat 4.1 logs on my NT workstation. Notice there are two "null" entries... while, both the filter as well as the DataSource work. My tomcat 4.1 setup on RHL 7.3 box shows me the nulls too, but the DataSource doesn't work there (no, I'm not trying to mix two topics together).
>
> Anybody got any idea why there is this null entry in the log messages?

I wouldn't worry about these.

Consider what happens when the code that parses your XML file encounters a
<filter> element.  First, it creates an object of the corresponding class
(FilterDef), then it configures the properties of that object based on the
nested <filter-name> (and so on) elements.  The debugging log prints out
the toString() of the object at that time, and is simply showing you that
the default values for some of the String properties on these
configuration objects are null.

Craig


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>