1、Tomcat启动报unable to start within 45 seconds错误解决办法
1.错误描述
Server Tomcat v8.0 Server at localhost was unable to start within 45 seconds. If the server requires more time, try increasing the timeout in the server editor.
2.解决办法
(1)找到tomcat
(2)双击tomcat,打开页面设置timeouts时间为450
2、eclipse 提示:An internal error occurred during: "Building workspace". GC overhead limit exceeded
最近公司给了一个服务端的项目让学习研究相关代码,结果导进eclipse后就出现了以前没有出现过的一个异常现象,eclipse一直显示正在bulideworkspace,eclipse运行很缓慢,什么都做不了几乎,卡的不行,紧接着出现了下面的界面
然后两秒后又出现了让离开workspace的提示,说是执行GC要:
百度搜索了一大堆后,弄明白了问题出现的原因:是Eclipse默认配置内存太小,需要更改Eclipse安装文件夹下的eclipse.ini文件。
解决办法:打开eclipse安装目录下的eclipse.ini文件,默认是如下的
修改如下:
-Xms512m
-Xmx1024m
第一个是最小的初始化内存,第二个是最大的占有内存
还可以加上 -XX:MaxPermSize=1024m这个意思是在编译文件时一直占有最大内存
贴一个修改好的eclipse.ini配置代码:
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v20150204-1316
-product
org.eclipse.epp.package.jee.product
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
256M
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
--launcher.appendVmargs
-vmargs
-Dosgi.requiredJavaVersion=1.6
-Xms512m
-Xmx1024m
-XX:MaxPermSize=1024m
然后重启Eclipse,一切搞定!
3、eclipse出现An internal error occurred during: "Building workspace". Java heap space 错误
出现这个错误,eclipse 会卡死,以及自动退出
解决方案
工程根目录 找到项目中.project文件
删除这两处
第一处:
<buildCommand>
<name>org.eclipse.wst.jsdt.core.javascriptValidator</name>
<arguments>
</arguments>
<ildCommand>
第二处:
<nature>org.eclipse.wst.jsdt.core.jsNature</nature>
4、解决Failed to start component [StandardEngine[Catalina].StandardHost[localhost]]的方法
1.问题描述:
用Tomcat启动一个Maven项目时,启动不起来,报错如下:
03-Dec-2019 20:32:21.358 严重 [localhost-startStop-1] org.apache.catalina.core.ContainerBase.addChildInternal ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/fendo-SSM]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:162)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:753)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:729)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1129)
at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1871)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.catalina.LifecycleException: Failed to start component [org.apache.catalina.webresources.StandardRoot@7822458a]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:162)
at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4969)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5099)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
... 10 more
Caused by: org.apache.catalina.LifecycleException: Failed to initialize component [org.apache.catalina.webresources.JarResourceSet@58b14405]
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:135)
at org.apache.catalina.webresources.StandardRoot.startInternal(StandardRoot.java:707)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
... 13 more
Caused by: java.lang.IllegalArgumentException: java.util.zip.ZipException: invalid LOC header (bad signature)
at org.apache.catalina.webresources.AbstractSingleArchiveResourceSet.initInternal(AbstractSingleArchiveResourceSet.java:113)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
... 16 more
Caused by: java.util.zip.ZipException: invalid LOC header (bad signature)
at java.util.zip.ZipFile.read(Native Method)
at java.util.zip.ZipFile.access$1400(ZipFile.java:60)
at java.util.zip.ZipFile$ZipFileInputStream.read(ZipFile.java:717)
at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(ZipFile.java:419)
at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:158)
at sun.misc.IOUtils.readFully(IOUtils.java:65)
at java.util.jar.JarFile.getBytes(JarFile.java:425)
at java.util.jar.JarFile.getManifestFromReference(JarFile.java:193)
at java.util.jar.JarFile.getManifest(JarFile.java:180)
at org.apache.catalina.webresources.AbstractSingleArchiveResourceSet.initInternal(AbstractSingleArchiveResourceSet.java:111)
... 17 more
开始一直关注 “Failed to start component ”这个错误,网上找了很多方法,都不行,后来看到还有一个错误是“java.util.zip.ZipException: invalid LOC header (bad signature)”,然后从这里入手,发现是mvn下载的jar包邮问题导致的,下面给出解决办法
2.解决方法
右键项目->Run as-> Maven test, 这里一定要注意:不要看到控制台打印出BUILD SUCCESS就认为是没问题的,要仔细看控制台的信息,如果出现
[WARNING] 读取C:\Users\PC\.m2\repository\org\springframework\spring-jdbc\4.3.12.RELEASE\spring-jdbc-4.3.12.RELEASE.jar时出错; invalid LOC header (bad signature)
[WARNING] 读取C:\Users\PC\.m2\repository\org\springframework\spring-aspects\4.3.12.RELEASE\spring-aspects-4.3.12.RELEASE.jar时出错; invalid LOC header (bad signature)
[WARNING] 读取C:\Users\PC\.m2\repository\javax\servlet\jstl\1.2\jstl-1.2.jar时出错; invalid LOC header (bad signature)
类似于如上的信息,就找到本地maven仓库的地址把出错的jar包删除掉,然后重新maven update一下,重新下载jar包,再启动就没问题了
注意:如果运行maven test没出现的话,先maven clean一下再执行maven test