Eclipse强制关闭导致无法再次启动的解决方法
2017-11-14 23:59
477 查看
Eclipse强制关闭后,重新再启动时,发现eclipse无法再次启动
查看workspace的.plugin文件夹下的.log文件,报错如下:
!ENTRY org.eclipse.ui 4 0 2017-11-14 23:55:00.898
!MESSAGE Error occurred during status handling
!STACK 0
java.lang.NullPointerException
at org.eclipse.ui.internal.statushandlers.StatusHandlerRegistry.<init>(StatusHandlerRegistry.java:61)
at org.eclipse.ui.internal.statushandlers.StatusHandlerRegistry.getDefault(StatusHandlerRegistry.java:91)
at org.eclipse.ui.statushandlers.StatusManager.getStatusHandler(StatusManager.java:135)
at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:189)
at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:231)
at org.eclipse.ui.statushandlers.StatusManager$StatusManagerLogListener.logging(StatusManager.java:305)
at org.eclipse.core.internal.runtime.RuntimeLog.logToListeners(RuntimeLog.java:160)
at org.eclipse.core.internal.runtime.PlatformLogWriter.logged(PlatformLogWriter.java:100)
at org.eclipse.equinox.log.internal.ExtendedLogReaderServiceFactory.safeLogged(ExtendedLogReaderServiceFactory.java:86)
at org.eclipse.equinox.log.internal.ExtendedLogReaderServiceFactory.logPrivileged(ExtendedLogReaderServiceFactory.java:205)
at org.eclipse.equinox.log.internal.ExtendedLogReaderServiceFactory.log(ExtendedLogReaderServiceFactory.java:178)
at org.eclipse.equinox.log.internal.ExtendedLogServiceFactory.log(ExtendedLogServiceFactory.java:65)
at org.eclipse.equinox.log.internal.ExtendedLogServiceImpl.log(ExtendedLogServiceImpl.java:87)
at org.eclipse.equinox.log.internal.LoggerImpl.log(LoggerImpl.java:54)
at org.eclipse.core.internal.runtime.Log.log(Log.java:62)
at org.eclipse.ui.internal.WorkbenchPlugin.log(WorkbenchPlugin.java:822)
at org.eclipse.ui.internal.EarlyStartupRunnable.handleException(EarlyStartupRunnable.java:81)
at org.eclipse.core.runtime.SafeRunner.handleException(SafeRunner.java:75)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:44)
at org.eclipse.ui.internal.Workbench$55.run(Workbench.java:2551)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
解决方法1:删掉整个eclipse的workspace,但这样会导致之前建立的项目都不见了,得重建
解决方法2:删除org.eclipse.ui.workbench,这样也可以重启,目前没有看到这样解决会有什么隐患。
查看workspace的.plugin文件夹下的.log文件,报错如下:
!ENTRY org.eclipse.ui 4 0 2017-11-14 23:55:00.898
!MESSAGE Error occurred during status handling
!STACK 0
java.lang.NullPointerException
at org.eclipse.ui.internal.statushandlers.StatusHandlerRegistry.<init>(StatusHandlerRegistry.java:61)
at org.eclipse.ui.internal.statushandlers.StatusHandlerRegistry.getDefault(StatusHandlerRegistry.java:91)
at org.eclipse.ui.statushandlers.StatusManager.getStatusHandler(StatusManager.java:135)
at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:189)
at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:231)
at org.eclipse.ui.statushandlers.StatusManager$StatusManagerLogListener.logging(StatusManager.java:305)
at org.eclipse.core.internal.runtime.RuntimeLog.logToListeners(RuntimeLog.java:160)
at org.eclipse.core.internal.runtime.PlatformLogWriter.logged(PlatformLogWriter.java:100)
at org.eclipse.equinox.log.internal.ExtendedLogReaderServiceFactory.safeLogged(ExtendedLogReaderServiceFactory.java:86)
at org.eclipse.equinox.log.internal.ExtendedLogReaderServiceFactory.logPrivileged(ExtendedLogReaderServiceFactory.java:205)
at org.eclipse.equinox.log.internal.ExtendedLogReaderServiceFactory.log(ExtendedLogReaderServiceFactory.java:178)
at org.eclipse.equinox.log.internal.ExtendedLogServiceFactory.log(ExtendedLogServiceFactory.java:65)
at org.eclipse.equinox.log.internal.ExtendedLogServiceImpl.log(ExtendedLogServiceImpl.java:87)
at org.eclipse.equinox.log.internal.LoggerImpl.log(LoggerImpl.java:54)
at org.eclipse.core.internal.runtime.Log.log(Log.java:62)
at org.eclipse.ui.internal.WorkbenchPlugin.log(WorkbenchPlugin.java:822)
at org.eclipse.ui.internal.EarlyStartupRunnable.handleException(EarlyStartupRunnable.java:81)
at org.eclipse.core.runtime.SafeRunner.handleException(SafeRunner.java:75)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:44)
at org.eclipse.ui.internal.Workbench$55.run(Workbench.java:2551)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
解决方法1:删掉整个eclipse的workspace,但这样会导致之前建立的项目都不见了,得重建
解决方法2:删除org.eclipse.ui.workbench,这样也可以重启,目前没有看到这样解决会有什么隐患。
相关文章推荐
- eclipse在异常关闭后,导致无法启动workspace问题的解决
- eclipse上一次没有正确关闭,导致启动的时候卡死错误解决方法
- eclipse在异常关闭后,导致无法启动workspace问题的解决
- eclipse上一次没有正确关闭,导致启动的时候卡死错误解决方法
- eclipse在异常关闭后,导致无法启动workspace问题的解决
- eclipse在异常关闭后,导致无法启动workspace问题的解决
- eclipse异常关闭情况下,再次启动服务器报端口被占用解决方法
- 解决:eclipse 非正常关闭,导致无法正常启动
- eclipse在异常关闭后,导致无法启动workspace问题的解决
- 意外关闭Eclipse导致无法启动的解决办法
- eclipse上一次没有正确关闭,导致启动的时候卡死错误解决方法
- eclipse上一次没有正确关闭,导致启动的时候卡死错误解决方法
- 关于解决关闭eclipse之后tomcat无法启动以及找不到javax.servlet的方法
- eclipse上一次没有正确关闭,导致启动的时候卡死错误解决方法
- eclipse在异常关闭后,导致无法启动workspace问题的解决
- eclipse在异常关闭后,导致无法启动workspace问题的解决
- Eclipse闪退/打不开/无法启动/一闪而过打解决方法
- Oracle表空间文件损坏导致的数据库异常关闭并启动失败问题的解决方法
- 04_Weblogic之受管服务器:配置受管服务器,启动受管服务器,解决因为强制关闭Weblogic之后导致启动有问题的问题,配置boot.properties
- 由于NFS服务没有启动,导致XenServer 6.5无法连接NAS存储问题的解决方法