fglterry 发表于 2016-5-19 23:01:04

求助 刚搭好环境后运行有错误 访问不了主页

本帖最后由 fglterry 于 2016-5-20 22:04 编辑

小白一名,环境搭建一直都失败,但还是继续努力。 最后搭建到运行这一步,实在解决不了,向各位求助,谢谢。
在run as tomcat server 后 出现以下错误,导致主页访问不了。 (已经参考常见问题贴问题18   但未解决。)

五月 19, 2016 10:45:13 下午 org.apache.catalina.core.StandardContext listenerStart
严重: Exception sending context initialized event to listener instance of class org.jeecgframework.web.system.listener.OnlineListener
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'taskDemoServiceTaskCronTrigger' defined in file : Invocation of init method failed; nested exception is org.hibernate.exception.SQLGrammarException: could not extract ResultSet



五月 19, 2016 10:45:13 下午 org.apache.catalina.core.StandardContext startInternal
严重: Error listenerStart
五月 19, 2016 10:45:13 下午 org.apache.catalina.core.StandardContext startInternal
严重: Context startup failed due to previous errors
五月 19, 2016 10:45:13 下午 org.apache.catalina.core.ApplicationContext log
信息: Closing Spring root WebApplicationContext
五月 19, 2016 10:45:13 下午 org.apache.catalina.core.ApplicationContext log
信息: Shutting down log4j
五月 19, 2016 10:45:13 下午 org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
严重: The web application registered the 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.
五月 19, 2016 10:45:13 下午 org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
严重: The web application registered the 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.
五月 19, 2016 10:45:13 下午 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application appears to have started a thread named but has failed to stop it. This is very likely to create a memory leak.
五月 19, 2016 10:45:13 下午 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application appears to have started a thread named but has failed to stop it. This is very likely to create a memory leak.
五月 19, 2016 10:45:13 下午 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application appears to have started a thread named but has failed to stop it. This is very likely to create a memory leak.
五月 19, 2016 10:45:13 下午 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application appears to have started a thread named but has failed to stop it. This is very likely to create a memory leak.
五月 19, 2016 10:45:13 下午 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application appears to have started a thread named but has failed to stop it. This is very likely to create a memory leak.
五月 19, 2016 10:45:13 下午 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application appears to have started a thread named but has failed to stop it. This is very likely to create a memory leak.
五月 19, 2016 10:45:13 下午 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application appears to have started a thread named but has failed to stop it. This is very likely to create a memory leak.
五月 19, 2016 10:45:13 下午 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application appears to have started a thread named but has failed to stop it. This is very likely to create a memory leak.
五月 19, 2016 10:45:13 下午 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application appears to have started a thread named but has failed to stop it. This is very likely to create a memory leak.
五月 19, 2016 10:45:13 下午 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application appears to have started a thread named but has failed to stop it. This is very likely to create a memory leak.
五月 19, 2016 10:45:13 下午 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application appears to have started a thread named but has failed to stop it. This is very likely to create a memory leak.
五月 19, 2016 10:45:13 下午 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application appears to have started a thread named but has failed to stop it. This is very likely to create a memory leak.
五月 19, 2016 10:45:13 下午 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application appears to have started a thread named but has failed to stop it. This is very likely to create a memory leak.
五月 19, 2016 10:45:13 下午 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application appears to have started a thread named but has failed to stop it. This is very likely to create a memory leak.
五月 19, 2016 10:45:13 下午 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application appears to have started a thread named but has failed to stop it. This is very likely to create a memory leak.
五月 19, 2016 10:45:13 下午 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application appears to have started a thread named but has failed to stop it. This is very likely to create a memory leak.
五月 19, 2016 10:45:13 下午 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application appears to have started a thread named but has failed to stop it. This is very likely to create a memory leak.
五月 19, 2016 10:45:13 下午 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application appears to have started a thread named but has failed to stop it. This is very likely to create a memory leak.

补充:20160520
在启动tomcat 是还有一个警告:
五月 20, 2016 10:03:52 下午 org.apache.tomcat.util.digester.SetPropertiesRule begin
警告: {Server/Service/Engine/Host/Context} Setting property 'source' to 'org.eclipse.jst.jee.server:jeecg' did not find a matching property.

问题是否和这个有关????






页: [1]
查看完整版本: 求助 刚搭好环境后运行有错误 访问不了主页