startup failed due to previous errors

[Matthew Hersee]

Hi all,

(I hope you can help and that i have posted this in the best place)

When i restart tomcat my web application generates the following errors

Apache.log

2006-12-19 15:10:30,190 - ERROR (org.apache.catalina.core.StandardContext:4111) - Error filterStart
2006-12-19 15:10:30,190 - ERROR (org.apache.catalina.core.StandardContext:4111) - Error filterStart
2006-12-19 15:10:30,190 - ERROR (org.apache.catalina.core.StandardContext:4130) - Context [/qsm] startup failed due to previous errors
2006-12-19 15:10:30,190 - ERROR (org.apache.catalina.core.StandardContext:4130) - Context [/qsm] startup failed due to previous errors

Stdout

-------------------------------------------------
QSM Application Initialized.
-------------------------------------------------
Introspector flushed.
LogManager shutdown.
Log factory released.
-------------------------------------------------
QSM Application Destroyed.
-------------------------------------------------

I cannot find any more debug information in any of the logs so am at a loss as to where to look next. I have checked the xml files and they all seem fine and have worked previously. We are using log4j to manage our logs

1 - is there a way to get more information about these errors?

2 - i dont have a catalina.log file anywhere, can someone tell we how to configure this? will this log file contain any useful info?

3 - is log4j restricting the amount of logs i can see? can i turn it off somehow to enable me to see absolutely everything in a stdout?


Sorry for so many questions but i have been looking into this for hours now and my patience is long gone,

Thanks in advance for any help

Matt

[Bear Bibeault]

apache.log? Are you running Tomcat in concert with Apache?

What Tomcat version?

All Tomcat versions I am aware of write their output to $CATALINA_HOME/logs/catalina.out

From what you've posted so far it looks as though some filters that you have declared cannot be loaded.

[Matthew Hersee]

Hi there,

Thanks for the response

1 - my catalina_home variable is set to "C:\apache-tomcat", all of my logs live in C:\apache-tomcat\logs

2 - Tomcat version is 5

3 - apache.log - i think this comes back to my ignorance about logs and how they are configured, i have no idea why that file has that name. We arent doing anything clever using Apache - we use IIS as our webserver

4 - yep, i think it is the filters, but my problem is that i have no log that gives further detail about the reason the filter failed to load correctly. Can i change log4j/web.xml somehow to get more detail about these errors?

Ta

Matt

[Bear Bibeault]

If you don't have a catalina.out log, then someone has set things up differently than the norm and so I'm not sure what to tell you.

Things I'd check are to make sure that the filter class files are where the web.xml says that they will be and other such set up conditions.

Exception messages should be emitted to stdout regardless of any log4j settings so there's not much you can do there except to confer with your admin to find out why you're not getting the stdout logged someplace where you can find it.

[Navin Nd Singh]

Check if your project WEB-INF directory has contect.xml file or not. If it has, make sure that it has the correct name of project with /. Eg. your project name is TestPortlet, then it should be /TestPortlet

[Bear Bibeault]

Please read this.

[Nishan Patel]

Hi,

Have you use database connection with your application... ???

Because I have also face same problem with same error ........ But after I found that It was database connection problem....

So, please make sure your database connection if you use ......

[ujjwal soni]

Hi,

Thats not a database issue.......


you're probably missing some environment variable that is used to setup class
loaders, such as CATALINA_BASE or CATALINA_HOME etc

Cheers!!!

[Nishan Patel]

Hi,

As ujjwal soni Says ...

Thats not a database issue.......

No I told possibly database problem ........ And once I am also facing with same problem and I found that it was database problem ........

So, you can not says sure about it....