For anyone unfortunate enough to get the same NullPointerException, what 
seems to happen is the following:

In Tomcat 5.5.9 if an exception is thrown in ServletFilter.init it may not 
produce any logging output of any sort.
In this case I use Spring which tends to be pretty good at reporting errors, 
so I suspect that it is more severe than a lack of logging statements.
I didn't get any logged exceptions under 5.5.9, but under 5.5.12 I did.

"hv @ Fashion Content" <[EMAIL PROTECTED]> skrev i en meddelelse 
news:[EMAIL PROTECTED]
>I have xerxesImpl and xml-apis in tomcat/common/endorsed
>
> might that be causing some trouble?
>
> Upgraded to 5.5.12 but the config failure persists
>
> "hv @ Fashion Content" <[EMAIL PROTECTED]> skrev i en meddelelse 
> news:[EMAIL PROTECTED]
>> The error information on context.xml parsing is very sparse to say the 
>> least...
>>
>> SEVERE: Error deploying configuration descriptor ROOT.xml
>> java.lang.NullPointerException
>>        at 
>> org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:574)
>>        at 
>> org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:536)
>>        at 
>> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:471)
>>        at 
>> org.apache.catalina.startup.HostConfig.start(HostConfig.java:1102)
>>        at 
>> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
>>        at 
>> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
>>        at 
>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1020)
>>        at 
>> org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
>>        at 
>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1012)
>>        at 
>> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
>>        at 
>> org.apache.catalina.core.StandardService.start(StandardService.java:450)
>>        at 
>> org.apache.catalina.core.StandardServer.start(StandardServer.java:683)
>>        at org.apache.catalina.startup.Catalina.start(Catalina.java:537)
>>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>        at 
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>        at 
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>        at java.lang.reflect.Method.invoke(Method.java:585)
>>        at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:271)
>>        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:409)
>>
>> As I have 3 different hosts defined, I am not sure which one it refers 
>> to. It seems though that all three fail with this message. Even so the 
>> third seems to be working fine, while the other two are not.
>>
>> This is the content of one of them
>> <context
>>   path="" docBase="ROOT" reloadable="true">
>> <!--   reloadable="true"  autoDeploy="true" deployOnStartup="true" -->
>>   <Valve className="org.apache.catalina.valves.AccessLogValve"
>>                  directory="logs"  prefix="blingon_test_log." 
>> suffix=".txt"
>>                  pattern="common" resolveHosts="false"/>
>>
>> Any ideas as to what makes HostConfig fail ? I assume it is a parsing 
>> error, but since there is no logging statement in line 566, I don't know 
>> which. 




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to