A very frequent problem.
As Nathan Pruett has already mentioned, it is because of Spring container launching as listener (specified in web.xml) cannot be started.
To know the exact reason of this failure you have to look through spring logs. As spring uses commons-logging (not log4j) as its default you have to tell him to use log4j.
This can be done by creating file commons-logging.properties on the classpath and entering there the following line:
After that don't forget to specify the logging level for spring in your log4j.properties:
we have problem because of Jar version. In our development environment one developer use higher version jar and at the same thing when we are configure to out system it shows error. So, just change and make Jar version same, JDK same , tomcat same solve the problem.