3349 [localhost-startStop-1] INFO org.hibernate.cfg.SettingsFactory - Named query checking : enabled
3349 [localhost-startStop-1] INFO org.hibernate.cfg.SettingsFactory - Check Nullability in Core (should be disabled when Bean Validation is on): enabled
4049 [localhost-startStop-1] INFO org.quartz.core.QuartzScheduler - Scheduler scheduler_$_NON_CLUSTERED shutting down.
4049 [localhost-startStop-1] INFO org.quartz.core.QuartzScheduler - Scheduler scheduler_$_NON_CLUSTERED paused.
4053 [localhost-startStop-1] INFO org.quartz.core.QuartzScheduler - Scheduler scheduler_$_NON_CLUSTERED shutdown complete.
Mar 02, 2016 4:01:45 PM org.apache.catalina.core.StandardContext startInternal
SEVERE: One or more listeners failed to start. Full details will be found in the appropriate container log file
Mar 02, 2016 4:01:45 PM org.apache.catalina.core.StandardContext startInternal
SEVERE: Context [/heximobile] startup failed due to previous errors
Mar 02, 2016 4:01:45 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesJdbc
SEVERE: The web application [/heximobile] registered the JDBC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
Mar 02, 2016 4:01:45 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads
SEVERE: The web application [/heximobile] appears to have started a thread named [MySQL Statement Cancellation Timer] but has failed to stop it. This is very likely to create a memory leak.
Mar 02, 2016 4:01:45 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads
SEVERE: The web application [/heximobile] appears to have started a thread named [Timer-1] but has failed to stop it. This is very likely to create a memory leak.
Mar 02, 2016 4:01:45 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /usr/apache-tomcat-7.0.67/webapps/heximobile has finished in 50,024 ms
Mar 02, 2016 4:01:45 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-nio-1303"]
Mar 02, 2016 4:01:45 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
Mar 02, 2016 4:01:45 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 50731 ms
1.web.xml文件，这个文件中定义了很多web服务启动需要的类、xml文件，如果这些找不到就会发生startup failed due to previous errors错误。
2.如果使用spring的话，在applicationContext.xml中定义的类、xml文件找不到也会报这个错误。
3。如果使用ibatis的话，在SqlMapConfig.xml中定义的xml文件找不到也会报这个错误。
总结的经验就是一定要把配置文件中定义的每条信息弄清楚，不要拿来别人的代码就使用，这样就会解决这个问题。
是不是你搭建tomcat服务器出现问题了
首先，重新去官网下个tomcat，把本地的删除掉，在直接新建一个项目，看看能不能启动，能启动，在用这个tomcat启动你的项目，能启动，就说明你的tomcat有问题，如果不可以，就说明是项目的问题，检查项目里面是不是少了什么配置文件。
去tomcat目录下看看logs/localhost.日期log，里面有提示信息