eclipse - Tomcat Not Starting after adding postgresql jar -
i using apache tomcat server eclipse. when added postgresql jar tomcat, fails start , ends on timeout message: "server tomcat v7.0 server @ localhost unable start within 45 seconds. if server requires more time, try increasing timeout in server editor". console output shown below:
sep 04, 2013 12:39:50 org.apache.catalina.core.aprlifecyclelistener init info: apr based apache tomcat native library allows optimal performance in production environments not found on java.library.path: c:\program files (x86)\java\jre7\bin;c:\windows\sun\java\bin;c:\windows\system32;c:\windows;c:/program files (x86)/java/jre7/bin/client;c:/program files (x86)/java/jre7/bin;c:/program files (x86)/java/jre7/lib/i386;c:\program files\miktex 2.9\miktex\bin;c:\program files (x86)\miktex 2.9\miktex\bin;c:\program files (x86)\pc connectivity solution\;c:\windows\system32;c:\windows;c:\windows\system32\wbem;c:\windows\system32\windowspowershell\v1.0\;c:\program files (x86)\quicktime\qtsystem\;c:\windows\system32\gs\gs8.71\bin;c:\svn\bin;e:\apache-maven-3.0.5\bin;c:\program files\java\jdk1.7.0_02\bin;c:\jexcel;c:\program files (x86)\openssh\bin;c:\osmdata;c:\osm2pgsql;c:\osm2pgsql\x64\;c:\program files\matlab\r2010a\runtime\win64;c:\program files\matlab\r2010a\bin;e:\eclipse;;. sep 04, 2013 12:39:50 org.apache.tomcat.util.digester.setpropertiesrule begin warning: [setpropertiesrule]{server/service/engine/host/context} setting property 'source' 'org.eclipse.jst.jee.server:scriptsynth' did not find matching property. sep 04, 2013 12:39:50 org.apache.coyote.abstractprotocol init info: initializing protocolhandler ["http-bio-8080"] sep 04, 2013 12:39:50 org.apache.coyote.abstractprotocol init info: initializing protocolhandler ["ajp-bio-8009"] sep 04, 2013 12:39:50 org.apache.catalina.startup.catalina load info: initialization processed in 1162 ms sep 04, 2013 12:39:50 org.apache.catalina.core.standardservice startinternal info: starting service catalina sep 04, 2013 12:39:50 org.apache.catalina.core.standardengine startinternal info: starting servlet engine: apache tomcat/7.0.41 sep 04, 2013 12:39:57 org.apache.catalina.core.applicationcontext log info: no spring webapplicationinitializer types detected on classpath sep 04, 2013 12:39:57 org.apache.catalina.core.applicationcontext log info: initializing spring root webapplicationcontext 00:39:57.572 [localhost-startstop-1] info o.s.web.context.contextloader - root webapplicationcontext: initialization started 00:39:57.761 [localhost-startstop-1] info o.s.w.c.s.xmlwebapplicationcontext - refreshing root webapplicationcontext: startup date [wed sep 04 00:39:57 ist 2013]; root of context hierarchy 00:39:57.884 [localhost-startstop-1] info o.s.b.f.xml.xmlbeandefinitionreader - loading xml bean definitions class path resource [applicationcontext.xml] 00:39:58.656 [localhost-startstop-1] info o.s.w.c.s.xmlwebapplicationcontext - bean 'org.springframework.orm.jpa.vendor.hibernatejpavendoradapter#1c212b0' of type [class org.springframework.orm.jpa.vendor.hibernatejpavendoradapter] not eligible getting processed beanpostprocessors (for example: not eligible auto-proxying) 00:39:58.727 [localhost-startstop-1] info o.s.w.c.s.xmlwebapplicationcontext - bean 'datasource' of type [class org.springframework.jndi.jndiobjectfactorybean] not eligible getting processed beanpostprocessors (for example: not eligible auto-proxying) 00:39:58.727 [localhost-startstop-1] info o.s.w.c.s.xmlwebapplicationcontext - bean 'datasource' of type [class org.apache.tomcat.dbcp.dbcp.basicdatasource] not eligible getting processed beanpostprocessors (for example: not eligible auto-proxying) 00:39:58.752 [localhost-startstop-1] info o.s.o.j.localcontainerentitymanagerfactorybean - building jpa container entitymanagerfactory persistence unit 'default' 00:39:59.167 [localhost-startstop-1] info o.h.annotations.common.version - hcann000001: hibernate commons annotations {4.0.2.final} 00:39:59.182 [localhost-startstop-1] info org.hibernate.version - hhh000412: hibernate core {4.2.5.final} 00:39:59.185 [localhost-startstop-1] info org.hibernate.cfg.environment - hhh000206: hibernate.properties not found 00:39:59.188 [localhost-startstop-1] info org.hibernate.cfg.environment - hhh000021: bytecode provider name : javassist 00:39:59.236 [localhost-startstop-1] info org.hibernate.ejb.ejb3configuration - hhh000204: processing persistenceunitinfo [ name: default ...] 00:39:59.461 [localhost-startstop-1] info o.h.s.j.c.i.connectionproviderinitiator - hhh000130: instantiating explicit connection provider: org.hibernate.ejb.connection.injecteddatasourceconnectionprovider
when remove postgresql jar tomcat's lib folder, starts fine before.
postgresql seems running can conenct pgadmin
any ideas on how fix this?
hey had same problem hope added new jar tomcat directory.... 400 kb
small one. , sorted in tomcat/lib/
directory bigger smaller , start time double 30 seconds 60 seconds
. driving me nuts. later sorted tomcat/lib/
directory smaller bigger , 32 seconds think here problem called branch prediction
please take topics.
why faster process sorted array unsorted array?
and
http://en.wikipedia.org/wiki/branch_predictor
i hope can helps somebody..
Comments
Post a Comment